Channel
@dnsprt
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
22subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002132401738 |
|---|---|
| Type | Channel |
| Username | @dnsprt |
| Description | заказы открыты mtrl; @MGNHELP @evehlp @strchelp @chaoshlp @oreolle @passion_hlp асенда/даша she/her |
| Created | Between 1 November 2023 and 20 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/dnsprt |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 13:32 | 22 | no change |
| 10 Aug 2026, 19:15 | 22 | first reading |
16 posts held, back to 20 May 2024 — 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 pageof 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 16 posts for this entry, the most recent from 28 August 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
113 reactions across 11 posts, in 6 distinct kinds. The most used accounts for 29.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5332569920846711389 | 33 | 29.2% | |
| 🤬 | 30 | 26.5% | |
| custom 5474444407304372159 | 29 | 25.7% | |
| custom 5278576332190532309 | 11 | 9.73% | |
| custom 5316701554286285005 | 8 | 7.08% | |
| 🤮 | 2 | 1.77% |
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 areTelegram’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 11 of the 16 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 113reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 20 May 2024 to 28 August 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
ребят давайте быть умничками и отмечать мой порт или мой пинт как вдохновение а еще не забудьте прочитать что полное/частичное копирование запрещено! у меня жопа горит с этой работы я скоро ее со всех площадок удалю <333333^^^ всем пака
🤬4custom 54744444073043721594
насколько будет хайп щас закрыться
🤬2custom 54744444073043721592
ебаать у меня др супер!!!₽₽₽
🤬2custom 54744444073043721592
Sticker, posted without a caption
🤬3custom 54744444073043721591
YNGPSS 🔤 din.osaur prtfl 3.07
custom 53325699208467113899custom 54744444073043721595🤬4
Sticker, posted without a caption
File, posted without a caption
custom 53325699208467113895custom 54744444073043721593🤬2
Sticker, posted without a caption
File, posted without a caption
custom 53325699208467113894🤬1custom 54744444073043721591
🌟CMH 🔤 din.osaur prtfl nw.era ведь у меня с собой ✝ – бензопила а 👎 hueta designer ✅ owner info 🌟Вдоль и поперек бензопила 🐲 anon. message
custom 53325699208467113899🤬7custom 54744444073043721597
Sticker, posted without a caption
何千 の箱 ? ˚⌒ thank u! полное копирование запрещено! также если вдохновляетесь - отмечайте мой порт 🔯 – dinosaur’s glamor. . dn.com
custom 53325699208467113896🤬4custom 54744444073043721594🤮2
Showing the 12 most recent of 16 posts we hold for @dnsprt. 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.
Citation-graph rank — 643,663 of 1,350,102entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
Named by 3 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 August 2026 — this entry's latest reading, not the date you are reading this.
“dinosaur.” (@dnsprt), 22 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/dnsprt.
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.