Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝘚𝘱𝘰𝘰𝘬𝘺 𝘔𝘰𝘯𝘵𝘩 [𝘈𝘴𝘬!]

Channel

𝘚𝘱𝘰𝘰𝘬𝘺 𝘔𝘰𝘯𝘵𝘩 [𝘈𝘴𝘬!]

@spookyaskmonth

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

50subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002301171182
TypeChannel
Username@spookyaskmonth
CreatedBetween 1 September 2024 and 31 December 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
On Telegramt.me/spookyaskmonth

Growth

508 August 2026 — 50 subscribers10 August 2026 — 50 subscribers8 August 202610 August 2026
2 measurements spanning 2 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 49–51 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 12:0050no change
8 Aug 2026, 17:1550first reading

Engagement

14 posts held, back to 31 December 2024the 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 14 posts for this entry, the most recent from 17 March 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
64
Links
2

Lifetime counters from Telegram’s own channel header, read 10 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

487 reactions across 14 posts, in 19 distinct kinds. The most used accounts for 26.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💋13126.9%
💘10220.9%
8617.7%
🍓367.39%
❤‍🔥357.19%
🍾214.31%
😢173.49%
💔142.87%
🔥102.05%
🥰102.05%
😭91.85%
👍51.03%
💅30.616%
20.411%
🎄20.411%
🎅10.205%
🎉10.205%
👾10.205%
🥴10.205%

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

Measured over the 14 most recent posts we hold, published 31 December 2024 to 17 March 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

17 Mar 2025, 13:21 UTC476 views35 reactionsread 10 August 2026
Photo

фш:: нарисуйте портрет персонажа, если бы тот был из реальности #Morgana

💋20💘86🍓1

11 Feb 2025, 19:31 UTC653 views47 reactionsread 10 August 2026
Photo

фш:: нарисуйте три стикера в стиле вк стикеров с вашим персонажем #Jaune

💋23🥰9🍓4💘4🔥32💅2

9 Feb 2025, 08:02 UTC545 views36 reactionsread 10 August 2026
Photo

фш:: нарисуйте портрет персонажа, если бы тот был из реальности #Carmen

💋1711🍓5💘2🔥1

8 Feb 2025, 09:32 UTC703 views39 reactionsread 10 August 2026
Photo

🎤:: Думала ли ты завести себе нового партнёра? фш: убегаем от дедлайна! ответ скетчем >_< #Lila

💘21💋8🔥4🍓32😢1

1 Feb 2025, 08:06 UTC482 views63 reactionsread 10 August 2026
Photo

🎤:: Ваша с мужем история любви? #Jaune

28💘17💋10❤‍🔥5🍓2💅1

31 Jan 2025, 19:59 UTC445 views33 reactionsread 10 August 2026
Photo

фш:: перерисовать картинку под персонажа #Carmen

🍓16💋7💘63❤‍🔥1

31 Jan 2025, 08:06 UTC395 views51 reactionsread 10 August 2026
Photo

🎤:: Каким ножом удобнее разделять конечности у человека? Сделай сигма фейс пж #Bob

💘27💋127❤‍🔥3🍓1🥴1

30 Jan 2025, 06:44 UTC533 views29 reactionsread 10 August 2026
Photo

🎤:: Каково быть младшим ребенком в семье?? Старший брат тебя не задирает?? +фш (убегаем от дедлайна! ответ скетчем >_<) #Morgana #флэшмоб

💋166💘6🍓1

29 Jan 2025, 08:19 UTC363 views15 reactionsread 10 August 2026

#Уход #Roy К сожалению, Рой покидает наш аск по собственному желанию... удачи отвечающему, спасибо за работу в аске! 🤩\\ Роль свободна для бронирования!

😢14👍1

28 Jan 2025, 15:46 UTC383 views17 reactionsread 10 August 2026

#Уход #Ross К сожалению, Росс покидает наш аск... 🤩\\ Роль свободна для бронирования!

💔13👍4

19 Jan 2025, 14:44 UTC586 views15 reactionsread 10 August 2026

#Уход #Kevin К сожалению, Кевин покидает наш аск по собственному желанию... удачи отвечающему, спасибо за работу в аске! 🤩\\ Роль свободна для бронирования!

😭9💘2😢2💋1💔1

16 Jan 2025, 08:20 UTC609 views40 reactionsread 10 August 2026
Photo

🎤:: Вы всегда так строги со своим сыном? #Carmen

❤‍🔥21💋7💘6🍓2🔥21🥰1

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

Citation-graph rank — 928,014 of 1,481,243entries 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.

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

“𝘚𝘱𝘰𝘰𝘬𝘺 𝘔𝘰𝘯𝘵𝘩 [𝘈𝘴𝘬!]” (@spookyaskmonth), 50 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/spookyaskmonth.

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.