Sticker, posted without a caption

Channel
GYMPIRE COMUNITY : data
@berkasgympirecomunity
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
2subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001610412059 |
|---|---|
| Type | Channel |
| Username | @berkasgympirecomunity |
| Created | Between 1 December 2021 and 27 November 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/berkasgympirecomunity |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 06:19 | 2 | no change |
| 9 Aug 2026, 16:31 | 2 | first reading |
Engagement
20 posts held, back to 27 November 2022 — 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 20 posts for this entry, the most recent from 29 December 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 GYMPIRE COMUNITY. 𝐏𝐀𝐆𝐄 30 ━━━━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━━━━━━━ 01. 𝗗´𝗦𝗔𝗦𝗧𝗘𝗥 𝗦𝗤𝗨𝗔𝗗 • @OFCDISASTERSQ • @partnerxster_bot • active 02. OFC AEXTHRONE • @AEXTHRONE • @mppsaexthrone_bot • active 03. INVINYTY OFC • @INVINYTYOFC • @Invinytympps_bot • active 04. OFC DOUGLAND • @OFCDOUGLAND • @MPPSDGLNDBOT • active …
Sticker, posted without a caption
𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 GYMPIRE COMUNITY. 𝐏𝐀𝐆𝐄 29 ━━━━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━━━━━━━ 01. 𝐖äitíng 𝐅ôr 𝐋ovē ; 𝗚𝗔𝗥𝗗£𝗡 • @WAITINGFORLOVERP • @WFLMPPS_BOT • active 02. 𝐂𝐎𝐔𝐋𝐃𝐈𝐍𝐄𝐒𝐒 • @officialconess • @mppsconessbot • active 03. 𝐎𝐅𝐂.𝐂𝐎𝐌𝐏𝐋𝐄𝐗 𝐈𝐑𝐄𝐍𝐄 • @ofccomplexirene • @mpscxirenebot • active 04. 797 KOTA JAEHYUN • @kotajaehyunofc • @partne…
Sticker, posted without a caption
𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 GYMPIRE COMUNITY. 𝐏𝐀𝐆𝐄 28 ━━━━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━━━━━━━ 01. 𝗥𝗔𝗩𝗢𝗥𝗦 𝗚𝗔𝗡𝗞 • @RAVORSGANK • @PSRAVORS_BOT • libur 02. 𝕿𝐎𝐗𝐎𝐏𝐇𝐈𝐋𝐈𝐓𝐄 𝐎𝐅𝐂 • @TOXOPHILITEOFC • @MPPSTXPHBOT • libur 03. TONGKRONGAN 1985 • @TONGKRONGAN1985 • @FRIEND1985BOT • active 04. 𝗦𝗖𝗔𝗥𝗬 𝗗𝗘𝗔𝗧𝗛𝗟𝗘𝗦𝗦 𝗖𝗥𝗘𝗪 • @SDCOFC • @sdcmpps_bot • active 05. …
Sticker, posted without a caption
𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 𝐆𝐘𝐌𝐏𝐈𝐑𝐄 𝐂𝐎𝐌𝐔𝐍𝐈𝐓𝐘 𝐏𝐀𝐆𝐄 27 ━━━━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━━━━━━━ 01. 𝐒𝐌𝐀𝐏𝐈 𝐎𝐅𝐂 • @officiallsmapi • @Pssmapibot • rombak 02. 𝐕𝐀𝐍𝐆𝐒𝐓𝐄𝐑 • @OFCVANGSTERR • @mppsvangster_bot • active 03. VŒMOPH OFC • @ofcvoemoph • @voemophpsbot • active 04. Orphic • @BIGORPHIC • @MppsOrphcBot • active 05. 𝗙𝗘𝗡𝗥𝗘𝗨𝗦 𝗨𝗡𝗜𝗧𝗘𝗗 • @post…
Sticker, posted without a caption
𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 𝐆𝐘𝐌𝐏𝐈𝐑𝐄 𝐂𝐎𝐌𝐔𝐍𝐈𝐓𝐘 𝐏𝐀𝐆𝐄 26 ━━━━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━━━━━━━ 01. 𝐇𝐎𝐌𝐄 𝐒𝐄𝐗 𝐀𝐑𝐄𝐀 18+ • @OFCHOMESEXAREA • @PARTNERHSEXBOT • active 02. Chondrites Kindergarten • @ChonkinOfficial • @MppsChonkin_bot • active 03. 𝐎𝐅𝐂 𝐂𝐈𝐆𝐄𝐙 • @OFCCRICLEGZ • @mppsCIGEZbot • active 04. 𝐉𝐔𝐍𝐆 𝐅𝐀𝐌𝐒 • @JUNGFAMSS • @KANTORTHEJUNGPS_BOT …
Sticker, posted without a caption
𝐏𝐀𝐑𝐓𝐍𝐄𝐑𝐒𝐇𝐈𝐏 𝐆𝐘𝐌𝐏𝐈𝐑𝐄 𝐂𝐎𝐌𝐔𝐍𝐈𝐓𝐘 𝐏𝐀𝐆𝐄 25 ━━━━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━━━━━━━ 01. 𝗥𝗢𝗬𝗔𝗟 𝗠𝗘𝗗𝗜𝗖𝗔𝗟 𝗖𝗘𝗡𝗧𝗘𝗥 • @ROYALMEDICALCENTER • @PCHMPPSBOT • active SUB UNIT • 𝐑𝐎𝐘𝐀𝐋 𝐊𝐈𝐍𝐃𝐄𝐑𝐆𝐀𝐑𝐓𝐄𝐍 • @ROYALKINDERGARTEN • vacum 02. 𝐎𝐅𝐂 𝐀𝐗𝐓𝐌𝐎𝐓𝐎𝐑 • @ofcaxtmotor • @mppsaxtmotorbot • active 03. 𝗢𝗙𝗖 𝗩𝗘𝗡𝕯𝗔𝗟𝗔𝗦𝗔𝗥 • @ofcvendalasar • @Mppsvedanlasarbot …
Showing the 12 most recent of 20 posts we hold for @berkasgympirecomunity. 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
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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
- 107
- 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
- 107
- vacant every time we have ever looked
@berkasgympirecomunity named 107 handles 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.
named in 2 posts, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
named in 1 post, 15 August 2026 – 15 August 2026
57 more handles are in this same list but not shown individually here — capped at 50.
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.
“GYMPIRE COMUNITY : data” (@berkasgympirecomunity), 2 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/berkasgympirecomunity.
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.