Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝓞. 𝗀𝗂ꭑ𝖾𐓣 ♡

Channel

𝓞. 𝗀𝗂ꭑ𝖾𐓣 ♡

@yebbuc

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

1subscribers

+0 since we began measuring on 15 August 2026

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

Register entry

Telegram ID-1003790074122
TypeChannel
Username@yebbuc
Created27 April 2026measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live24 August 2026
Measurements held2
Confirmed unchanged2 times, most recently 24 August 2026
On Telegramt.me/yebbuc

Growth

115 Aug 2026, 10:32 — 1 subscribers16 Aug 2026, 18:17 — 1 subscribers15 Aug 2026, 10:3216 Aug 2026, 18:17
2 measurements spanning 1 day. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 18:171no change
15 Aug 2026, 10:321first reading

Engagement

18 posts held, back to 27 April 2026the 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 18 posts for this entry, the most recent from 25 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

25 Jul 2026, 16:17 UTC48 viewsread 15 August 2026

🤩- send ur best selca here!ㅤㅤㅤㅤㅤㅤㅤㅤ+ id di mono &. nama panggilan :3

25 Jun 2026, 12:51 UTC130 viewsread 15 August 2026

send ur best selca here! 💕 ㅤㅤ🧸 + id di mono &. nama panggilan ㅤmain game M B G

11 Jun 2026, 13:08 UTC198 viewsread 15 August 2026

send ur best selca here! 💕 ㅤㅤㅤ🧸+ id di mono &. nama panggilan

4 Jun 2026, 18:07 UTC213 viewsread 15 August 2026

ꨄ︎. Mufièns Feb &. March 2026 𐚁. Mufièns April 2026 ⨾༊󠀺. Mufièns May 2026 𝜗ৎ. Mufièns June 2026 ᝰ 🦢 .ᐟ Mufièns July 2026 ᢉ𐭩. Mufièns August-Sept 2026.

9 May 2026, 02:33 UTC230 viewsread 15 August 2026

🍍 BATCH 3 :: ✅ https://t.me/jBugatti/s/1901 https://t.me/genitle/s/779 https://t.me/IXYEONJUN/s/713 https://t.me/ellagronss/s/15 https://t.me/oHpenulis/s/30 https://t.me/Songznim/s/5 https://t.me/iFloats/s/861 https://t.me/suddenv/s/269 https://t.me/iBrooklynne/s/2535 https://t.me/hiArtiss/s/1697 https://t.me/seonghxn/s/247 https://t.me/cutielovyie/s/71 https://t.me/Lotuskisseu/s/553 https://t.me/Chanyoukng/s/643 htt

7 May 2026, 17:25 UTC167 viewsread 15 August 2026

Bonjour! 👀💖 If there's any dislike, hit me up :: @iJuueen, so we can unsave nicely. <3

7 May 2026, 16:30 UTC188 viewsread 15 August 2026

❤️ HFW LINKS 7 May - 10 May <3 🍓 BATCH 1 :: ✅ https://t.me/kenkhainn/s/635 https://t.me/yuuhax/s/504 https://t.me/defaulyt/s/1638 https://t.me/zchoisoobin/s/1488 https://t.me/twobelii/s/6151 https://t.me/pqoetr/s/726 https://t.me/iEnergique/s/653 https://t.me/kakntin/s/866 https://t.me/Ieejtaeyong/s/1357 https://t.me/tecnager/s/422 https://t.me/Aprhoditje/s/3058 https://t.me/milkikta/s/380 https://t.me/angelenism/s/

Showing the 12 most recent of 18 posts we hold for @yebbuc. 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 — 747,164 of 1,626,711entries 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 7 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.

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

“𝓞. 𝗀𝗂ꭑ𝖾𐓣 ♡” (@yebbuc), 1 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/yebbuc.

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.