23 Nov 2024, 16:20 UTC70 viewsread 14 August 2026
ada yg rindu kga???
Channel
@TOXOPHILITEOFC
@TOXOPHILITEOFC
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1subscribers
+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 | -1001852641907 |
|---|---|
| Type | Channel |
| Username | @TOXOPHILITEOFC |
| Created | 18 July 2023 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/TOXOPHILITEOFC |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 08:17 | 1 | no change |
| 7 Aug 2026, 04:01 | 1 | first reading |
Engagement
3 posts held, back to 18 July 2023 — 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 3 posts for this entry, the most recent from 23 November 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
Showing the 3 most recent of 3 posts we hold for @TOXOPHILITEOFC. 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 — 978,888 of 1,480,688entries 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 29 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.
[ VAKUM ] 𝐊𝐈𝐍𝐆'𝐒 𝐂𝐑𝐎𝐒𝐒 𝐒𝐐
@KINGSCROSSQ · 243 postsPARTNER LIVI
@partnerlivi · 92 postsARSIP MPPS 𝐃𝐈𝐎𝐍𝐘𝐒𝖀𝐒 𝐒𝐐 𝟐𝟏
@arsipdns21 · 11 postARSIP GLAUCIO
@arsipglaucio · 21 post𝐀𝗿𝘀𝗶𝗽 𝐕𝗲𝗹𝗼𝘁𝗿𝗮𝗻 𝐆𝗮𝗻𝗸
@Arsipvlt · 41 postBLACKJACK CORP PS
@BJPARTNERS · 91 post𝐉𝐈𝐒𝐎𝐎'𝐒 𝐌𝐀𝐍𝐒𝐈𝐎𝐍 𝐏𝐀𝐑𝐓𝐍𝐄𝐑
@jsmmps · 91 postPARTNERSHIP 𝐂𝐑𝐘𝐋A̸𝐍𝔇
@LISTPSCRYLAND · 21 post𝐌edpart. 𝐎'𝐉𝐎𝐄
@medpart_ojoe · 31 postMEDPART ESU
@MedpartEsu · 31 postteman rkc
@medpartrkcity · 41 post𝐌Ø𝐔𝐓𝐙𝐈𝐐
@MOUTZIQ · 781 post𝐃𝐄𝐀𝐓𝐇𝐋𝐄𝐒𝐒 𝐖𝐎𝐋𝐅 𝐌𝐏𝐏𝐒
@MPPSDEATHLESSWOLF · 41 postMPPS 𝐃𝐑₳Ӿ𝐈𝐎𝐍
@mppsdxn · 21 postLIST PS
@mppskurir · 31 postPASKTH PARTNERSHIP
@mppspaskth · 21 post𝐏𝐄𝐑𝐙𝐄𝐔𝐒 𝐔𝐍𝐈𝐕𝐄𝐑𝐒𝐄
@OFCPERZEUS · 631 postTHE BEATLES
@OFCTHEBEATLESSQ · 1571 post.
@psbrigezz · 21 postDATA PARTNERSHIP
@psofcmeriadoc · 21 postARSIP PARTNER RNJ
@REPNAMJAINFO · 81 postTKSD PARTNERSHIP
@TKSDARSIP · 11 postWΛRD DĒXTØR PS
@warddextorps · 41 postWattana Partnership
@wattanapartner · 71 post
@KINGSCROSSQ · 243 postsPARTNER LIVI
@partnerlivi · 92 postsARSIP MPPS 𝐃𝐈𝐎𝐍𝐘𝐒𝖀𝐒 𝐒𝐐 𝟐𝟏
@arsipdns21 · 11 postARSIP GLAUCIO
@arsipglaucio · 21 post𝐀𝗿𝘀𝗶𝗽 𝐕𝗲𝗹𝗼𝘁𝗿𝗮𝗻 𝐆𝗮𝗻𝗸
@Arsipvlt · 41 postBLACKJACK CORP PS
@BJPARTNERS · 91 post𝐉𝐈𝐒𝐎𝐎'𝐒 𝐌𝐀𝐍𝐒𝐈𝐎𝐍 𝐏𝐀𝐑𝐓𝐍𝐄𝐑
@jsmmps · 91 postPARTNERSHIP 𝐂𝐑𝐘𝐋A̸𝐍𝔇
@LISTPSCRYLAND · 21 post𝐌edpart. 𝐎'𝐉𝐎𝐄
@medpart_ojoe · 31 postMEDPART ESU
@MedpartEsu · 31 postteman rkc
@medpartrkcity · 41 post𝐌Ø𝐔𝐓𝐙𝐈𝐐
@MOUTZIQ · 781 post𝐃𝐄𝐀𝐓𝐇𝐋𝐄𝐒𝐒 𝐖𝐎𝐋𝐅 𝐌𝐏𝐏𝐒
@MPPSDEATHLESSWOLF · 41 postMPPS 𝐃𝐑₳Ӿ𝐈𝐎𝐍
@mppsdxn · 21 postLIST PS
@mppskurir · 31 postPASKTH PARTNERSHIP
@mppspaskth · 21 post𝐏𝐄𝐑𝐙𝐄𝐔𝐒 𝐔𝐍𝐈𝐕𝐄𝐑𝐒𝐄
@OFCPERZEUS · 631 postTHE BEATLES
@OFCTHEBEATLESSQ · 1571 post.
@psbrigezz · 21 postDATA PARTNERSHIP
@psofcmeriadoc · 21 postARSIP PARTNER RNJ
@REPNAMJAINFO · 81 postTKSD PARTNERSHIP
@TKSDARSIP · 11 postWΛRD DĒXTØR PS
@warddextorps · 41 postWattana Partnership
@wattanapartner · 71 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“@TOXOPHILITEOFC” (@TOXOPHILITEOFC), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/TOXOPHILITEOFC.
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.