Channel

DAGGER EVENT ORGANIZER

@DAGGERORGANIZER

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

2subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID	-1002063095736
Type	Channel
Username	@DAGGERORGANIZER
Created	10 May 2024 — measured — dated from the channel’s first post
First recorded	13 August 2026
Last confirmed live	13 August 2026
Measurements held	2
On Telegram	t.me/DAGGERORGANIZER

Growth

2 measurements spanning 7 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 1–3 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
13 Aug 2026, 20:07	2	no change
6 Aug 2026, 22:00	2	first reading

Engagement

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

Citation-graph rank

Citation-graph rank — 405,755 of 1,481,502entries 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.

Mentions

Named by 108 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

Named by

Channels on the register whose posts name this channel's handle.

𝐖𝐇𝐘𝐕𝐄𝐑𝐍
@OFCWHYVERN · 404 posts BUBAR
@seindahsenyumanmu · 2344 posts 𝐄unwoniest
@eunwoniest · 153 posts 𝐎𝐅𝐂 𝐙𝐀𝐂𝐇Ø𝐑𝐘
@ZACHORYOFFICIAL · 903 posts MEMORIES//𝐎𝐅𝐂 𝐃𝐄𝐕𝐈𝐋𝐒 𝐀𝐍𝐃 𝐁𝐀𝐑 𝐀𝐍𝐆𝐄𝐋𝐒
@avadachannel · 352 posts [MEMORIES] 𝐂𝐔𝐋𝐓𝐔𝐑𝐀 𝐇𝐈𝐆𝐇 𝐒𝐂𝐇𝐎𝐎𝐋
@culturaofc · 2,1432 posts 𝐃𝐑𝐀𝐗𝐄𝐑𝐓𝐘
@DRAXERTYOFC · 172 posts 𝐄𝐌𝐄𝐑𝐀𝐋𝐃 𝐍𝐈𝐆𝐇𝐓𝐂𝐋𝐔𝐁 𝐈𝐧𝐜.
@EMERALDNIGHTCLUB · 372 posts 𝐄𝐌𝐄𝐑𝐀𝐋𝐃 𝐂𝐎𝐑𝐏𝐎𝐑𝐀𝐓𝐈𝐎𝐍
@EMERALDOFC · 1512 posts OFC 𝕳𝐈𝐆𝐖𝐀𝐘𝐌𝐀𝐍 [ VAKUM ]
@HIGWAYMANOFC · 162 posts Majalah B4U
@majalahb4u · 82 posts 𝐌𝐎𝐎𝐍𝐑𝐎𝐖 𝐒𝐂𝐇𝐎𝐎𝐋 || BUBAR
@MOONROWSCHOOL · 862 posts 𝐀𝐋𝐋𝐄𝐆𝐈𝐀𝐍𝐓 || 'MEMORIES'
@ofcallegiant · 2422 posts MEMORIES ♡
@OFCHYSMELAND · 162 posts ARSIP LØΔNJING_GΛNK❝🇲🇪
@ofcmppsloanjing · 2622 posts 𝗢𝗙𝗖 𝗥𝗞𝗝
@ofcrkj · 3452 posts 𝐒𝐐𝐔𝐀𝐃 𝕯𝐄𝐈𝐍𝐎𝐒🦖
@OfficialDeinos · 202 posts POSTER RIGEL
@officialrigel · 852 posts REXVENDER MPPS
@rexvendermpps · 672 posts CLOSE | 𝐑𝐎𝐘𝐀𝐋 𝐂𝐀𝐑𝐈𝐁𝐁𝐄𝐀𝐍 𝐇𝐎𝐒𝐏𝐈𝐓𝐀𝐋
@ROYALCARIBBEANHOSPITAL · 372 posts 𝐒𝐈𝐑 𝐀𝐍𝐃 𝐌𝐀'𝐀𝐌 𝐑𝐄𝐓𝐑𝐎
@SNMRETROSQ · 212 posts 𝐒𝐓𝐀𝐑𝐇𝐈𝐓𝐄𝐑
@STARHITEROFC · 302 posts Stylooenxt.🧚🏻‍♀️
@stylooenxt · 632 posts MPPS RESIDENT JAEMARK
@mppsresidentjaemark · 61 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.

Handles this channel named that no longer answer

Dead references: 1; handles named in this channel’s posts, vacant today
Evidenced gone: 0; we ourselves saw one of these resolve, at some point
Never seen alive: 1; vacant every time we have ever looked

@DAGGERORGANIZER named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.

Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.

Never seen alive

References a handle that is not a live channel — we have no record it ever was one.

@maguwrld
named in 1 post, 14 August 2026 – 14 August 2026

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

“DAGGER EVENT ORGANIZER” (@DAGGERORGANIZER), 2 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/DAGGERORGANIZER.

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.