Telegram RegisterThe public register of Telegram
Telegram profile photo for Dan1to NFT

Channel

Dan1to NFT

@Dan1toNFT

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

1,737subscribers

-311 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003083925265
TypeChannel
Username@Dan1toNFT
CreatedBetween 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live18 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/Dan1toNFT

Topic

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 16 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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

1,7372,0481,892.58 August 2026 — 2,048 subscribers8 August 2026 — 2,048 subscribers8 August 2026 — 2,044 subscribers11 August 2026 — 2,030 subscribers14 August 2026 — 2,010 subscribers17 August 2026 — 1,990 subscribers20 August 2026 — 1,939 subscribers24 August 2026 — 1,884 subscribers27 August 2026 — 1,868 subscribers30 August 2026 — 1,863 subscribers2 September 2026 — 1,848 subscribers6 September 2026 — 1,826 subscribers11 September 2026 — 1,808 subscribers14 September 2026 — 1,767 subscribers18 September 2026 — 1,737 subscribers8 August 202618 September 2026
15 measurements spanning 42 days, net -311. 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 1,690–2,095 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 17:391,737-30
14 Sept 2026, 12:181,767-41
11 Sept 2026, 07:361,808-18
6 Sept 2026, 16:421,826-22
2 Sept 2026, 13:141,848-15
30 Aug 2026, 14:541,863-5
27 Aug 2026, 04:031,868-16
24 Aug 2026, 05:281,884-55
20 Aug 2026, 21:141,939-51
17 Aug 2026, 22:381,990-20
14 Aug 2026, 23:082,010-20
11 Aug 2026, 10:332,030-14
8 Aug 2026, 13:122,044-4
8 Aug 2026, 01:502,048no change
8 Aug 2026, 01:492,048first reading

Engagement

20 posts held, back to 10 July 2026the 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

41 reactions across 9 posts, in 7 distinct kinds. The most used accounts for 36.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👨‍💻1536.6%
🔥1229.3%
🥰512.2%
37.32%
👏37.32%
🙉24.88%
🥱12.44%

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 9 of the 20 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 41 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 10 July 2026 to 6 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.

Recent posts

30 Jul 2026, 19:37 UTC285 views5 reactionsread 8 August 2026

Всіх давайте хотяби 16 грн розіграю

🥰5

30 Jul 2026, 19:36 UTC246 viewsread 8 August 2026
Forwarded from @erturnir

🌟🎀🌟🌟🌟🌟🌟🎀🌟🌟 🫥 𝐄𝐑𝐀𝐍𝐆𝐄𝐋(Соло)🫥 🌟🎀🌟🌟🌟🌟🌟🎀🌟🌟 🅰️ 🅰️𝐈𝐃 : завтра 🅰️𝐏𝐀𝐒𝐒 : завтра 🅰️𝐒𝐓𝐀𝐑𝐓 : завтра 21:00 🅰️𝐏𝐑𝐈𝐙𝐄: 100грн 🇺🇦 🅰️ за призом писати до @Kot_3b не забудьте зробити скрін 🎀Підписку на :Blyadi🎀

15 Jul 2026, 11:22 UTC410 views2 reactionsread 8 August 2026
Forwarded from @erturnirPhoto

➖➖Відкриття клану➖➖ ➖➖ Blyadi Team➖➖ КРИТЕРІЇ ВСТУПУ ДО КЛАНУ 👀 Вік: від 15 років 😎 Режим гри: «Класика Метро» 🤪 Активність: регулярний онлайн та участь у житті клану 7днів на змін 😉Так само набір гравців на практичні ігри Писати: @Kot_3b

🙉2

12 Jul 2026, 18:01 UTC455 viewsread 8 August 2026

🎉 Результаты розыгрыша: 🏆 Победители: 1. Anastasiia (@nasty_shiik888) 2. Николай (@NLinsky) ✔️Проверить результаты

11 Jul 2026, 19:05 UTC351 viewsread 8 August 2026
Forwarded from @SaltGiftsNft

🔠🔠🔠🔠🔠🔠🔠 3 переможці отримують по факелу 🔥 1 – NFT 2 – NFT 3 – NFT 😗🙂😉😄🥲: 🔗Саб: 𝗖𝗕𝗜𝗧 𝗡𝗙𝗧 Та кинути скрін сабу під пост, прошу підписуватись лише тому кому реально цікаво тема новин, тому що профілі не по темі, пусті та твінки всеодно буду видаляти‼️ Людям з 3+ рейтингом плачу 5 зірок додатково деталі ТУТ Рези: на 300 скрінів

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

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.

Mentions

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.

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

“Dan1to NFT” (@Dan1toNFT), 1,737 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/Dan1toNFT.

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.