Telegram RegisterThe public register of Telegram
Telegram profile photo for НФТИШНАЯ

Channel

НФТИШНАЯ

@tonknft

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

787subscribers

-13 since we began measuring on 14 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002656713675
TypeChannel
Username@tonknft
CreatedBetween 1 March 2025 and 10 June 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live11 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 11 October 2026
On Telegramt.me/tonknft

Topic

Gambling & betting — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.

Growth

787800793.514 August 2026 — 800 subscribers15 August 2026 — 799 subscribers23 August 2026 — 797 subscribers30 August 2026 — 796 subscribers9 September 2026 — 793 subscribers17 September 2026 — 790 subscribers1 October 2026 — 788 subscribers11 October 2026 — 787 subscribers14 August 202611 October 2026
8 measurements spanning 58 days, net -13. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 785–802 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Oct 2026, 11:59787-1
1 Oct 2026, 23:00788-2
17 Sept 2026, 16:19790-3
9 Sept 2026, 13:36793-3
30 Aug 2026, 16:22796-1
23 Aug 2026, 03:24797-2
15 Aug 2026, 19:17799-1
14 Aug 2026, 15:32800first reading

Engagement

18 posts held, back to 10 June 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 18 posts for this entry, the most recent from 12 June 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

210 reactions across 18 posts, in 6 distinct kinds. The most used accounts for 56.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 527826982614442194211856.2%
custom 52806154409287585993114.8%
🔥2210.5%
custom 5283228279988309088199.05%
custom 5280598054901145762167.62%
💩41.90%

Custom emoji. 4 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 18 of the 18 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 210 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 10 June 2025 to 12 June 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

12 Jun 2025, 17:01 UTC≈1,040 views7 reactionsread 14 August 2026

Posted without readable text

custom 52782698261444219425custom 52806154409287585991custom 52832282799883090881

10 Jun 2025, 19:41 UTC≈1,230 views21 reactionsread 14 August 2026

Все, запущу в ночь топ-розыгрыш 💝 Идем отдыхать, раздача продолжится завтра 🎰

custom 527826982614442194213🔥5custom 52832282799883090883

10 Jun 2025, 19:36 UTC≈1,200 views4 reactionsread 14 August 2026

Еще го фаст Х50 окуп 🎰 7️⃣7️⃣7️⃣

custom 52782698261444219424

10 Jun 2025, 19:32 UTC≈1,160 views4 reactionsread 14 August 2026

Го за ракету с окупом х50 🎰 🍇🍋7️⃣ Поехали

custom 52782698261444219424

10 Jun 2025, 19:29 UTC≈1,140 views25 reactionsread 14 August 2026

Реакций накидайте?🌚

custom 527826982614442194210custom 52806154409287585996custom 52832282799883090885🔥4

10 Jun 2025, 19:20 UTC≈1,130 views7 reactionsread 14 August 2026

Цифру до 150 мне

custom 52782698261444219427

10 Jun 2025, 19:20 UTC≈1,100 views4 reactionsread 14 August 2026

Да чет все отдыхать пошли видимо Ну давайте 3 ласта

custom 52782698261444219424

10 Jun 2025, 19:12 UTC≈1,060 views16 reactionsread 14 August 2026

Еще?

custom 52782698261444219429🔥4custom 52805980549011457623

10 Jun 2025, 19:06 UTC≈1,050 views5 reactionsread 14 August 2026
Photo

Выдал всем участникам, а вы сомневались?

custom 52782698261444219423🔥1custom 52832282799883090881

10 Jun 2025, 18:55 UTC939 views6 reactionsread 14 August 2026

🎰 🍇 BAR7️⃣ 3 победителя по 💝

custom 52806154409287585995custom 52782698261444219421

10 Jun 2025, 18:48 UTC940 views40 reactionsread 14 August 2026

35 реакций и до 3 победителей 🎰

custom 527826982614442194221custom 52805980549011457628custom 52806154409287585997💩3🔥1

Showing the 12 most recent of 18 posts we hold for @tonknft. 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.

Forward network

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.

Cite this entry

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 October 2026 — this entry's latest reading, not the date you are reading this.

“НФТИШНАЯ” (@tonknft), 787 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/tonknft.

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.