Telegram RegisterThe public register of Telegram
Telegram profile photo for services.

Channel

services.

@Dantes_Trafficc

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

17subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003831372974
TypeChannel
Username@Dantes_Trafficc
Created2 April 2026 — measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live8 October 2026
Measurements held2
On Telegramt.me/Dantes_Trafficc

Growth

177 August 2026 — 17 subscribers11 August 2026 — 17 subscribers7 August 202611 August 2026
2 measurements spanning 4 days. 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 16–18 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 20:3117no change
7 Aug 2026, 19:0517first reading

Engagement

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

What this channel posts

Links
1

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.

Reaction mix

188 reactions across 1 post, in 10 distinct kinds. The most used accounts for 21.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54429605403830757844121.8%
custom 54449150769202669373920.7%
custom 52514236606143806223317.6%
custom 53755938108415917522714.4%
custom 53168741990866906302211.7%
custom 5444901801176356474189.57%
custom 502654838999561164921.06%
custom 521778624984622805221.06%
custom 522001552255644560521.06%
custom 544528327587662463621.06%

Custom emoji. Every row above is a 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 1 of the 2 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 188 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 2 most recent posts we hold, published 2 April 2026 to 2 April 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

2 Apr 2026, 11:38 UTC≈1,330 views188 reactionsread 11 August 2026

💥ПРОДАМ РЕКЛАМУ В СЛЕДУЮЩИХ ПРОЕКТАХ📈 KH TEAM 6.3К ПДП KH CHAT 1.8К УЧАСТНИКОВ KH CRYPTO 1.5K ПДП KH FAM VK 1К УЧАСТНИКОВ KH SERVICES 2К УЧАСТНИКОВ 💵ПРАЙС - https://t.me/PRlCE_KH 🔥ЕСТЬ СКИДКИ🔥 🤙Связь: @ADMlN_KH

custom 544296054038307578441custom 544491507692026693739custom 525142366061438062233custom 537559381084159175227custom 531687419908669063022custom 544490180117635647418custom 50265483899956116492custom 52177862498462280522

Showing the 2 most recent of 2 posts we hold for @Dantes_Trafficc. 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.

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

“services.” (@Dantes_Trafficc), 17 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Dantes_Trafficc.

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.