Telegram RegisterThe public register of Telegram

Channel

$POOKHUIS MPPS

@spookyst

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

6subscribers

+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-1001546524636
TypeChannel
Username@spookyst
CreatedBetween 1 August 2021 and 13 December 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/spookyst

Growth

67 August 2026 — 6 subscribers12 August 2026 — 6 subscribers7 August 202612 August 2026
2 measurements spanning 6 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 5–7 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 19:476no change
7 Aug 2026, 01:446first reading

Engagement

20 posts held, back to 13 December 2021the 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 20 posts for this entry, the most recent from 15 February 2022. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Videos
1
Links
1

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

Recent posts

25 Dec 2021, 15:36 UTC124 viewsread 12 August 2026

ㅤ ❲ PARTNERSHIP SPOOKHUIS ៸៸ ❳ ( PAGE 13 ) ✦ ・ ・ ──────────── ・ ・ ✦ 01. ⎙ . ⎙ . ⎙ . ⎙ . 02. ⎙ . ⎙ . ⎙ . ⎙ . 03. ⎙ . ⎙ . ⎙ . ⎙ . 04. ⎙ . ⎙ . ⎙ . ⎙ . 05. ⎙ . ⎙ . ⎙ . ⎙ . 06. ⎙ . ⎙ . ⎙ . ⎙ . 07. ⎙ . ⎙ . ⎙ . ⎙ . 08. ⎙ . ⎙ . ⎙

13 Dec 2021, 17:24 UTC175 viewsread 12 August 2026

ㅤ ❲ PARTNERSHIP SPOOKHUIS ៸៸ ❳ ( PAGE 12 ) ✦ ・ ・ ──────────── ・ ・ ✦ 01. ⎙ . 𝐎𝐅𝐂 𝐊𝐋𝐀𝐍𝐇𝐈𝐓𝐀𝐌 ⎙ . @KLANHITAMSQ ⎙ . @mppskhmbot ⎙ . aktif 02. ⎙ . 𝐎𝐅𝐂. 𝐀𝐑𝐒𝐓𝐄𝐑𝐒🇻🇮 ⎙ . @OFCCARSTERS ⎙ . @arsterspsbot ⎙ . aktif 03. ⎙ . ⎙ . ⎙ . ⎙ . 04. ⎙ . ⎙ . ⎙ . ⎙ . 05. ⎙ . ⎙ . ⎙ . ⎙ . 06. ⎙ . ⎙ .

13 Dec 2021, 14:27 UTC106 viewsread 12 August 2026

ㅤ ❲ PARTNERSHIP SPOOKHUIS ៸៸ ❳ ( PAGE 11 ) ✦ ・ ・ ──────────── ・ ・ ✦ 01. ⎙ . 𝗝𝗔𝗘𝗥𝗢𝗦𝗘 𝗧❦︎𝗪𝗡 ⎙ . @JAEROSETOWN ⎙ . @jaerosetownmpps_bot ⎙ . aktif ☆☆ SUB UNIT : ⎙ . ROSÉANNE TOWN ⎙ . @ROSEANNETOWN ⎙ . aktif 02. ⎙ . 𝐎𝐅𝐂 𝐀𝐆𝐎𝐑𝐀 ⎙ . @AGORAOFC ⎙ . @mpagorabot ⎙ . aktif ☆☆ SUB UNIT : ⎙ . OLYMPIA PROMOTE ⎙ . @OLYMP

13 Dec 2021, 06:42 UTC69 viewsread 12 August 2026

ㅤ ❲ PARTNERSHIP SPOOKHUIS ៸៸ ❳ ( PAGE 1O ) ✦ ・ ・ ──────────── ・ ・ ✦ 01. ⎙ . 𝕭𝖚𝖑𝖑𝖊𝖙𝖕𝖗𝖔𝖔𝖋 𝖘𝖖 𝐂𝐡𝐚𝐧𝐞𝐥 ⎙ . @BULLETPROOFSQ ⎙ . @kantorbltprftrobot ⎙ . aktif ☆☆ SUB UNIT : ⎙ . 𝐈𝐌𝐌꩜𝐑𝐓𝐀𝐋 ℒ꩜𝐕𝐄 𝐓𝐌𝐎 ⎙ . @IMMORTALLOVETMO ⎙ . aktif 02. ⎙ . KAMPUNG JAEYONG ⎙ . @KAMPUNGJAEYONG ⎙ . @KJYMPPSBOT ⎙ . libur 03. ⎙ . LOVE LOCK COUPLE

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

Names

Channels on the register whose handles appear in this channel's posts.

OFC . BAJIGUR 🇦🇱
@B4JIGUROFC · 673
1 post
RPW. 𝗕𝖀𝗥𝗝𝗢 𝐊𝗧𝗛
@burjokthrpw · 72
1 post
Disband, OFC DEVLӨƧƬΛ 🇭🇲
@Devlosta · 1,061
1 post
DOMKTH OFC. memories
@DOMKATEHAOFC · 20
1 post
𝐇𝐔𝐍𝐓𝐄𝐑 𝐄𝐀𝐆𝐋𝐄
@EAGLEREDD · 1,854
1 post
VAKUM! 𝐅𝐋𝐎𝐑𝐄 𝐄𝐕𝐄𝐍𝐓 𝐎𝐑𝐆𝐀𝐍𝐈𝐙𝐄𝐑
@FLOREORGANIZER · 7,726
1 post
OFC. GRIXEN GANK
@grixenchannel · 177
1 post
ˑ ִ ֗ 𓉸 𝅦 ⸼ {MEMORIES} 𝗝𝗔𝗘𝗥𝗢𝗦𝗘𝗧𝗢𝗪𝗡; Nouvelle Ère Glorieuse.
@JAEROSETOWN · 476
1 post
𝐊𝐀𝐅𝐈𝐗 𝐅𝐀𝐌𝐒 𝟗𝟒 🇵🇲
@KAFIXFAMS · 34
1 post
HIRMIN ★ 𝗞𝗔𝗠𝗣𝗨𝗡𝗚 𝗝𝗔𝗘𝗬𝗢𝗡𝗚 ★
@KAMPUNGJAEYONG · 90
1 post
𝗞𝗛𝗠 𝗦𝗤
@klanhitamsq · 238
1 post
𝐊𝐎𝐒𝐓𝐀𝐍 𝐌𝐀𝐑𝐊𝐇𝐘𝐔𝐂𝐊
@kostanMH · 213
1 post
Moztex Oplink.
@moztexofc · 164
1 post
VAKUM. 𝐍𝐂𝐓 𝐕𝐈𝐋𝐋𝐀𝐆𝐄
@NCTVILLAGEOFC · 19
1 post
𝐆𝐄𝐓𝐇𝐄𝐑𝐏𝐄𝐍
@OFCGETHERPEN · 48
1 post
𝗛𝗢𝗨𝗦𝗘 𝗢𝗙 𝗖𝗔𝗥𝗗𝗦 𝗢𝗙𝗖
@OfcHouseOfCards · 1,379
1 post
VAKUM || 𝕶𝐎𝐌𝐏𝐋𝐄𝐊 𝖄𝐌𝐉𝐌
@OFCKOMPLEKYMJM · 53
1 post
𝟮𝟲𝟴. 𝗣𝗢𝗡𝗚𝗢 (bubar)
@ofcpojokngopi · 294
1 post
MEMORIES RIVALLEO
@OFCRIVALLEO · 135
1 post
Selesai.
@ofcshinjuku · 9
1 post
@.OFCTAEKOOKHOME
@OFCTAEKOOKHOME · 13
1 post
541. THE MONGRELS
@OFCTHEMONGRELS · 90
1 post
patma reborn
@OFFICIALWARKOP45 · 174
1 post
𝐃`ONGANIZER [ MEMORIES ]
@onlabelseo · 41
1 post

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

“$POOKHUIS MPPS” (@spookyst), 6 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/spookyst.

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.