Channel
@nutlegoct
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
313subscribers
+3 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003826993891 |
|---|---|
| Type | Channel |
| Username | @nutlegoct |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/nutlegoct |
Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 22 September 2026 and assigned it the closest of 31 fixed categories, at 49% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 16:16 | 313 | -4 |
| 26 Aug 2026, 11:22 | 317 | +6 |
| 19 Aug 2026, 15:55 | 311 | +3 |
| 13 Aug 2026, 00:13 | 308 | -2 |
| 12 Aug 2026, 05:45 | 310 | first reading |
9 posts held, back to 10 August 2026 — 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 9 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
163 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 33.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5280983575460612500 | 55 | 33.7% | |
| custom 5445405514940847050 | 48 | 29.4% | |
| custom 5368599701413193821 | 25 | 15.3% | |
| custom 5431678601894340968 | 23 | 14.1% | |
| custom 5267326185049724691 | 12 | 7.36% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 7 of the 9 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 163 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 10 August 2026 to 11 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
[ 🌟 ] — ☺️ун☺️ᴩᴇʍы ᴛуᴛ ᴄᴏбᴩᴀᴧи дᴧя ʙᴀᴄ ᴄᴀʍую-ᴄᴀʍую ᴨᴩᴇᴋᴩᴀᴄную ᴨᴏдбᴏᴩᴋу ᴋᴀнᴀᴧьчиᴋᴏʙ ᴨᴩᴏ нᴀɯих ᴧюбиʍых ᴀᴋᴛᴇᴩᴏʙ <33 дᴧя уюᴛных ʙᴇчᴇᴩᴏʙ и хᴏᴩᴏɯᴇᴦᴏ нᴀᴄᴛᴩᴏᴇния нᴀɯᴀ ᴨᴏдбᴏᴩᴋᴀ – иʍᴇннᴏ ᴛᴏ чᴛᴏ ʙᴀʍ нужнᴏ ! — [ 🌟 ]
custom 52809835754606125001
Signed ʏúɴsωе ⊹
Sticker, posted without a caption
Signed ʏúɴsωе ⊹
➖➖˚ 🤎 legostagram photos .‘ > < MY PRINCESS 🫵 и с этой красавицей мы встретимся уже в октябре .‘ i cant wait .
custom 528098357546061250011custom 53685997014131938215custom 54316786018943409682custom 52673261850497246911custom 54454055149408470501
Signed ʏúɴsωе ⊹
Sticker, posted without a caption
Signed ʏúɴsωе ⊹
➖➖meowgo 🌟 ⊹ twitter upd .‘ ♡ так хочется увидеть красотку на концерте ты буквально читаешь мои мысли окей .
custom 544540551494084705015custom 54316786018943409687custom 53685997014131938214custom 52809835754606125002
Signed ʏúɴsωе ⊹
🥳☕️☕️ ୧ поймали вкусяншек в сторис у пи'боя ; 🫳 натчичи & мяуго сладости .‘
custom 544540551494084705015custom 54316786018943409685custom 53685997014131938214custom 52809835754606125002
Signed ʏúɴsωе ⊹
⁘ LETS GO ; продажа билетов на концерт начнутся с 22 числа этого месяца .‘ < / 3
custom 528098357546061250016custom 53685997014131938216custom 52673261850497246914custom 54316786018943409683
Signed ʏúɴsωе ⊹
🥳🥳🥥 ೨ next — los angeles .‘ </3
custom 528098357546061250014custom 52673261850497246916custom 54316786018943409686
Signed ʏúɴsωе ⊹
🥳⊹ posted 🌫️ ` pao_ontopp ; — i never saw any beautiful faces like their okay bro .
custom 544540551494084705017custom 52809835754606125009custom 53685997014131938216custom 52673261850497246911
Signed ʏúɴsωе ⊹
Showing the 9 most recent of 9 posts we hold for @nutlegoct. 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.
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“⌗ cástle for nutlego .‘” (@nutlegoct), 313 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/nutlegoct.
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.