Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝗗𝗜𝗩𝗦𝗞𝗜𝗘

Channel

𝗗𝗜𝗩𝗦𝗞𝗜𝗘

@DIVSKIE

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

384subscribers

-1 since we began measuring on 11 November 2026

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

Register entry

Telegram ID-1003833844161
TypeChannel
Username@DIVSKIE
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 November 2026
Last confirmed live14 November 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/DIVSKIE

Growth

384385384.511 November 2026 — 385 subscribers11 November 2026 — 385 subscribers14 November 2026 — 384 subscribers11 November 202614 November 2026
3 measurements spanning 3 days, net -1. 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 384–385 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Nov 2026, 14:16384-1
11 Nov 2026, 20:22385no change
11 Nov 2026, 19:47385first reading

Engagement

11 posts held, back to 3 November 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.

ERR · 30 days
70.1%
avg views ÷ 384 subscribers
Avg views / post
269
11 posts measured
Reaction rate
18.2%
reactions ÷ views · ER floor
Posts in window
11
of 11 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 10 of 11 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 November 2026
Posts held11 (3 November 2026 – 11 November 2026)
Views total2,961
Reactions total537
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 20:22 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

537 reactions across 10 posts, in 11 distinct kinds. The most used accounts for 18.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 531430107988469082910018.6%
custom 531473062815389667510018.6%
custom 53143713584345548136812.7%
custom 53144926354260911276512.1%
custom 5316933323606485819539.87%
👻346.33%
🕊336.15%
☃285.21%
👀264.84%
🆒152.79%
💘152.79%

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

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

Telegram’s own ‘edited’ marker: 1 of 11 posts held from the last 30 days (9.09%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

11 Nov 2026, 17:39 UTC14 viewsread 11 November 2026
Forwarded from @rtsurs

#нарезки #cuts #lookingforalaska ˖ 🖤🖤 — аляска янг ࣪ (🤍)) — взяли? при использовании материала отмечать тт: r3ues ㅤ

Signed .

11 Nov 2026, 13:21 UTC149 views40 reactionsread 11 November 2026
Photo

🤩 🔤алисой 🔤анобан. 🔤🔤 стикеры (37) 🤍 #ЛалисойМанобан #нарезки 🔠зял(-а)? «+» в комм & @DIVSKIE

👀14custom 531693332360648581910custom 53147306281538966758custom 53143010798846908292☃1👻1🕊1🆒1

Signed .

10 Nov 2026, 14:34 UTC223 views68 reactionsread 11 November 2026
Photo

🤩 🔤лео 🔤ертори. 🔤🔤 стикеры (32) 🤍 #КлеоСертори #H2OПростоДобавьВоды #стикеры #цв 🔠зял(-а)? «+» в комм & @DIVSKIE

👻14custom 531473062815389667511🕊10💘5custom 53143713584345548135custom 53169333236064858195🆒4custom 53143010798846908294

Signed .

10 Nov 2026, 14:32 UTC283 views69 reactionsread 11 November 2026
Photo

🤩 🔤да 🔤ылдыз. 🔤🔤 стикеры (73) 🤍 #ЭдаЙылдыз #ПостучисьвМоюДверь #стикеры #цв 🔠зял(-а)? «+» в комм & @DIVSKIE

👻16custom 531449263542609112711custom 531473062815389667511🆒5👀4💘4custom 53143010798846908294custom 53143713584345548134

Signed .

10 Nov 2026, 14:29 UTC176 views68 reactionsread 11 November 2026
Photo

🤩 🔤апунцель. 🔤🔤 стикеры (33) 🤍 #Рапунцель #стикеры #цв 🔠зял(-а)? «+» в комм & @DIVSKIE

🕊17custom 531449263542609112711☃9👀4💘4🆒4custom 53143010798846908294custom 53143713584345548134

Signed .

7 Nov 2026, 16:08 UTC381 views52 reactionsread 11 November 2026
Photo

🤩 🔤эролайн Форбс. 🔤🔤 стикеры (80) 🤍 #КэролайнФорбс #стикеры #цв 🔠зял(-а)? «+» в комм & @DIVSKIE

custom 531473062815389667518☃12custom 531449263542609112711💘2🕊2custom 53143713584345548132custom 53169333236064858192👀1

Signed .

5 Nov 2026, 14:29 UTC592 views67 reactionsread 11 November 2026
Photo

🤩 🔤ристина Соколовская. 🔤🔤 стикеры (60) 🤍 #КристинаСоколовская #стикеры #цв 🔠зял(-а)? «+» в комм & @DIVSKIE

custom 531430107988469082932custom 531437135843455481318custom 531473062815389667511custom 53144926354260911273custom 53169333236064858193

Signed .

4 Nov 2026, 15:42 UTC358 views74 reactionsread 11 November 2026
Photo

🤩 🔤igaro. 🔤🔤 стикеры (40) 🤍 #figaro #стикеры #цв 🔠зял(-а)? «+» в комм & @DIVSKIE

custom 531430107988469082931custom 531437135843455481318custom 531693332360648581917custom 53147306281538966755custom 53144926354260911273

Signed .

4 Nov 2026, 15:39 UTC336 views69 reactionsread 11 November 2026
Photo

🤩 🔤садора Артиньян. 🔤🔤 стикеры (66) 🤍 #ИсадораАртиньян #стикеры #цв 🔠зял(-а)? «+» в комм & @DIVSKIE

custom 531473062815389667531custom 531449263542609112716custom 531430107988469082913custom 53143713584345548135custom 53169333236064858194

Signed .

4 Nov 2026, 11:00 UTC195 views10 reactionsread 11 November 2026
Photo

🔤🔤🔤🔤🔤🔤🔤🔤🔤🔤. Здесь вы можете написать свою идею для стикера, кого хотели бы видеть на канале. Чтобы оставить идею, нужно:: • написать имя и фамилию. • если из фильма/сериала/дорамы и т. д., указать название. • чтоб было проще предоставить фотографию. Стикеры и нарезки могут быть цв. и чб. Запросы мы больше не принимаем!!

custom 53143010798846908294custom 53143713584345548133custom 53169333236064858193

Signed .

3 Nov 2026, 17:56 UTC254 views20 reactionsread 11 November 2026
Photo

🤩 🔤ашей Лусс. 🔤🔤 стикеры (15) 🤍 #СашаЛусс #стикеры #цв 🔠зял(-а)? «+» в комм & @DIVSKIE

custom 53143713584345548138custom 53143010798846908295custom 53144926354260911275custom 53147306281538966751custom 53169333236064858191

Signed .

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

Named by 4 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.

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

“𝗗𝗜𝗩𝗦𝗞𝗜𝗘” (@DIVSKIE), 384 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/DIVSKIE.

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.