This reminds me I should update the map
Signed Lola

Channel
@myhugebutt
On this record: Growth · Engagement · Posts · Cite this entry
115subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001212112368 |
|---|---|
| Type | Channel |
| Username | @myhugebutt |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/myhugebutt |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 15:41 | 115 | -1 |
| 31 Aug 2026, 04:26 | 116 | +1 |
| 23 Aug 2026, 16:35 | 115 | -1 |
| 15 Aug 2026, 02:28 | 116 | -2 |
| 9 Aug 2026, 04:45 | 118 | no change |
| 8 Aug 2026, 12:33 | 118 | +1 |
| 7 Aug 2026, 13:09 | 117 | first reading |
18 posts held, back to 29 August 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 4 July 2023. An engagement rate over an empty window would be a number about nothing.
This reminds me I should update the map
Signed Lola
You're only this popular because you are dating a niche internet microcelebrity such as myself
Signed Lola
This is the one, for all you curious perverts. Even some of the other ones below have 4k and 3k. That's ludicrous. Y'all are some horny fuckers, I dig it
Signed Nadi
Ok so, usually I don't really mind. But, seeing that, through my channel, about 13,000 people have seen my ass through a single picture... I'm absolutely floored. Even the fact that there's like 40 of you in the chat feels like a lot, but looking at that... what even happened with that? Impressive. Thank you all, even if it was just a little thing you saw. Even my lesser viewed posts have like 500 people, so thats im…
Signed Nadi
Also! I'm probably going to start using this channel for shitposts more than my porn. I will still be posting things, eventually! It might take a bit, but I want to revive this channel
Signed Nadi
Me
Signed Nadi
I found a friend! They like showing off their ass too, and it's really nice, you should all look at it https://t.me/LewdShepStuff
Signed Nadi
Boo! Butt ghost jump scare 👻
Signed Lola
Places i've sucked the dweebs dick
Signed Lola
Nadi was just looking at a map of the US with me, saw "NV" and thought it stood for New Vegas
Signed Lola
I stole someone's stockings, she won't mind
Signed NeedsImprovement
Sticker, posted without a caption
Signed Lola
Showing the 12 most recent of 18 posts we hold for @myhugebutt. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 8 September 2026 — this entry's latest reading, not the date you are reading this.
“Nadi's nonsense” (@myhugebutt), 115 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/myhugebutt.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.