Posted without readable text
custom 52222895960705203289🔥4custom 53820763123556326222❤🔥1🍓1custom 51906815401698647971custom 52742205610425343251custom 53007723409241843211

Channel
@n1448tt
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
247subscribers
+19 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002010569358 |
|---|---|
| Type | Channel |
| Username | @n1448tt |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 2 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 2 September 2026 |
| On Telegram | t.me/n1448tt |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Sept 2026, 08:55 | 247 | -1 |
| 25 Aug 2026, 08:38 | 248 | +16 |
| 18 Aug 2026, 00:52 | 232 | +4 |
| 12 Aug 2026, 00:42 | 228 | no change |
| 11 Aug 2026, 20:17 | 228 | first reading |
4 posts held, back to 9 July 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 4 posts for this entry, the most recent from 4 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.
102 reactions across 4 posts, in 23 distinct kinds. The most used accounts for 31.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 32 | 31.4% | |
| custom 5222289596070520328 | 12 | 11.8% | |
| custom 5382076312355632622 | 6 | 5.88% | |
| ❤🔥 | 6 | 5.88% | |
| custom 5274220561042534325 | 5 | 4.90% | |
| custom 5325597694276683117 | 4 | 3.92% | |
| custom 5398014777077307662 | 4 | 3.92% | |
| custom 5416013086639288780 | 4 | 3.92% | |
| 💘 | 4 | 3.92% | |
| 🔥 | 4 | 3.92% | |
| custom 5440826895119715081 | 3 | 2.94% | |
| 😍 | 3 | 2.94% | |
| custom 5190681540169864797 | 2 | 1.96% | |
| custom 5285049470675870172 | 2 | 1.96% | |
| custom 5375341447153214980 | 2 | 1.96% | |
| custom 5375601004911823904 | 2 | 1.96% | |
| custom 5244900674738608700 | 1 | 0.98% | |
| custom 5246733264269384397 | 1 | 0.98% | |
| custom 5300772340924184321 | 1 | 0.98% | |
| custom 5305723836921060623 | 1 | 0.98% | |
| 3 further kinds | 3 | 2.94% |
Custom emoji. 15 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 4 of the 4 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 102 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 9 July 2026 to 4 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @n1448tt. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 4 most recent posts we hold for this entry, published 9 July 2026 to 4 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Posted without readable text
custom 52222895960705203289🔥4custom 53820763123556326222❤🔥1🍓1custom 51906815401698647971custom 52742205610425343251custom 53007723409241843211
🤍
❤11❤🔥4😍3custom 52222895960705203283custom 53255976942766831172custom 53820763123556326222custom 54160130866392887802custom 52742205610425343251
🙂🙂🙂🙂🙂🙂🙂🙂
❤9💘4custom 53980147770773076624custom 52742205610425343253custom 53255976942766831172custom 53756010049118239042custom 53820763123556326222❤🔥1
🎀
❤12custom 54408268951197150813custom 51906815401698647971custom 52449006747386087001custom 52467332642693843971custom 52850494706758701721custom 53237800211673629351custom 53753414471532149801
Showing the 4 most recent of 4 posts we hold for @n1448tt. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 2 September 2026 — this entry's latest reading, not the date you are reading this.
“𝓪𝓮𝓻𝓲𝓪𝓵_𝓷𝓪𝓼𝓽𝓽” (@n1448tt), 247 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/n1448tt.
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.