Nadeshot reveals six-figure Twitch revenue during Subathon, earning over $238,000 in 30 days

Nadeshot accidentally shows Twitch earnings of $238,146 during his subathon, revealing major income sources.


Pop Culture & Art November 12, 2024
Photo: Twitch / Nadeshot

During an ongoing subathon on Twitch, Nadeshot, founder of 100 Thieves, inadvertently exposed his impressive earnings, revealing a total of $238,146.23 USD accumulated over a 30-day period.

This hefty figure came from various revenue streams on Twitch, including subscriptions, ads, bits, and gifted subs. Among these, subscriptions proved to be the biggest moneymaker, with 48,027 subs contributing a significant portion to his earnings. Gifted subs alone brought in an impressive $116,771, showcasing the generous support of his fans throughout the marathon broadcast.

In addition to subscriptions, Nadeshot also benefited substantially from ad revenue. By running an average of nine minutes of ads per hour, he was able to earn an additional $71,784, demonstrating how ad integration during long streams can be a profitable strategy. His most lucrative day occurred on November 4, when he managed to generate over $30,000 in a single day, with the bulk of that income attributed to gifted subs, further underscoring the fan support that powers his earnings.

This revenue breakdown, however, doesn’t account for taxes. Although a portion of the income will be reduced by federal and other applicable taxes, Nadeshot’s recent relocation from Los Angeles to Texas could significantly lessen his overall tax burden, thanks to Texas’s absence of a state income tax. This strategic move allows Nadeshot to keep a larger share of his earnings, contrasting sharply with the higher tax obligations he would face in California. The relocation highlights a trend among high-income content creators who are choosing states with lower tax rates to maximize their income.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ