поздравляю с концом сезона товарищи!!
custom 54632726304317950535
Signed Трукодер 🌧

Channel
@truec0der
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
332subscribers
+9 since we began measuring on 8 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001151354329 |
|---|---|
| Type | Channel |
| Username | @truec0der |
| Created | Between 1 October 2018 and 30 June 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/truec0der |
Other / unclassifiable — 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 4 October 2026 and assigned it the closest of 31 fixed categories, at 82% 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 |
|---|---|---|
| 3 Oct 2026, 23:40 | 332 | -1 |
| 19 Sept 2026, 12:02 | 333 | +3 |
| 11 Sept 2026, 02:57 | 330 | +7 |
| 8 Sept 2026, 20:22 | 323 | first reading |
8 posts held, back to 2 September 2025 — 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 8 posts for this entry, the most recent from 8 September 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
181 reactions across 8 posts, in 12 distinct kinds. The most used accounts for 30.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5463180520563164187 | 55 | 30.4% | |
| custom 5463272630431795053 | 47 | 26.0% | |
| custom 5217792322929984907 | 32 | 17.7% | |
| 😍 | 19 | 10.5% | |
| 💘 | 10 | 5.52% | |
| 💅 | 5 | 2.76% | |
| ☃ | 4 | 2.21% | |
| 🥰 | 4 | 2.21% | |
| custom 5283005345415835804 | 2 | 1.10% | |
| custom 5368584651847771964 | 1 | 0.552% | |
| custom 5469716545959642271 | 1 | 0.552% | |
| 👏 | 1 | 0.552% |
Custom emoji. 6 of the rows above are 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 8 of the 8 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 181 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 2 September 2025 to 8 September 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.
поздравляю с концом сезона товарищи!!
custom 54632726304317950535
Signed Трукодер 🌧
Sticker, posted without a caption
custom 54631805205631641879☃3custom 52830053454158358041
Signed Трукодер ☔️
с новай годай 😎
custom 546318052056316418718☃1custom 54632726304317950531
Signed Трукодер ☔️
🐜
custom 521779232292998490732custom 54632726304317950533
Signed Трукодер ☔️
Поздравляю всех со стартом сезона!! 💅💅💅 Работы было очень много. Очень приятно наконец довести его до запуска 🥺
custom 546318052056316418721👏1custom 54697165459596422711
Signed Трукодер ☔️
За всю свою жизнь в Калининграде впервые погулял по Зеленоградску 🌟 Держите котиков (и немножко не котиков) 👋
custom 546327263043179505328💘5🥰4
Signed Трукодер ☔️
(видео немножка устаревшее, но всё равно держите Ромочку 💅)
😍19custom 54631805205631641877💘3custom 52830053454158358041custom 53685846518477719641custom 54632726304317950531
Signed Трукодер ☔️
С первым днём окончанием лета!!! (да, лето закончилось уже как два дня, и что вы мне сделаете, я в другом городе 😁) Это лето оказалось самым ярким на эмоции (как положительные, так и не очень) и новый жизненный опыт. Очень хочу подвести итоги и поделиться ими с вами 😇 В августе я слетал в Питер — это был мой первый в жизни самостоятельный полёт в другой город. Там встретился и пообщался с кучей разных людей. У меня…
custom 54632726304317950539💅5💘2
Signed Трукодер ☔️
Showing the 8 most recent of 8 posts we hold for @truec0der. 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 1 registered channel — 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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“Кусок воды 🦊💅” (@truec0der), 332 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/truec0der.
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.