Telegram RegisterThe public register of Telegram

Channel

leafxup confession

@Leafxupcf

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

508subscribers

+1 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-1003964789027
TypeChannel
Username@Leafxupcf
CreatedBetween 1 April 2026 and 12 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/Leafxupcf

Growth

507508507.57 Aug 2026, 19:15 — 507 subscribers8 Aug 2026, 04:16 — 507 subscribers8 Aug 2026, 08:22 — 508 subscribers7 Aug 2026, 19:158 Aug 2026, 08:22
3 measurements taken within a single day, net +1. 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 507–508 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 08:22508+1
8 Aug 2026, 04:16507no change
7 Aug 2026, 19:15507first reading

Engagement

19 posts held, back to 12 July 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.

ERR · 30 days
58.3%
avg views ÷ 508 subscribers
Avg views / post
296
13 posts measured
Reaction rate
7.11%
reactions ÷ views · ER floor
Posts in window
15
of 19 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held19 (12 July 20267 August 2026)
Views total3,852
Reactions total274
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 04:16 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
1m 29s
Average length
45s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

342 reactions across 17 posts, in 16 distinct kinds. The most used accounts for 31.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
10731.3%
custom 59948184401147368415014.6%
💘4613.5%
custom 59967269131276815653610.5%
custom 5305568908860738821349.94%
custom 5996817893419912450205.85%
🙏133.80%
custom 5384560018928467728123.51%
❤‍🔥61.75%
👀61.75%
custom 535966035405178583930.877%
🌚30.877%
🌭30.877%
custom 538187502012337267110.292%
10.292%
🆒10.292%

Custom emoji. 7 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 17 of the 19 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 342reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 12 July 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

7 Aug 2026, 12:21 UTC104 views30 reactionsread 8 August 2026

есть у кого удаленные видео с канала со стримами?? их же брльше было гораздо куда он все поудалял мои любимые были с щколой и лифтом в отеле... ... @leafxupcf | send take

16custom 599481844011473684110💘3custom 59967269131276815651

Signed лификсап тейки

4 Aug 2026, 00:50 UTC237 views16 reactionsread 8 August 2026
Video

Кто нибудь знает где найти эту песню или тут в тг у кого нибудь есть🥺🥺?? Я не шарю за ваши спотифаи яндекс музыки и. т. д. я тут в тг песенки слушаю, а песенку лификсапа реально охотой послушать она качает сукааа @leafxupcf | send take

14custom 59948184401147368412

Signed лификсап тейки

3 Aug 2026, 06:02 UTC260 views48 reactionsread 8 August 2026
Photo

ТВ NSFW ОЧЕНЬ ЖЕСТКОЕ УЖАС. ДЕТЯМ. НЕ. ПОКАЗЫВАТЬ !!!!!!!! мой маленький, к сожалению выкладывающий видео leafxup и его большой/маленький друг мишкфреде 🥰🥰🥰 первый раз рисую такое как ваммм? @nill1414 @leafxupcf | send take 🌂::Я так и знал,что после видео с мшк фреде кто то нарисует это.

custom 5305568908860738821328custom 59967269131276815656custom 59948184401147368412

Signed лификсап тейки

2 Aug 2026, 16:59 UTC235 views15 reactionsread 8 August 2026
Photo

лификсапчик 😋😋 тгк: https://t.me/Rinnmemr @leafxupcf | send take

custom 59967269131276815657💘6custom 59948184401147368412

Signed лификсап тейки

30 Jul 2026, 15:33 UTC261 views27 reactionsread 8 August 2026
Photo

соскучились тгк: https://t.me/szleepdarRR @leafxupcf | send take

custom 5996726913127681565139💘3custom 59948184401147368412

Signed лификсап тейки

25 Jul 2026, 19:50 UTC406 views14 reactionsread 8 August 2026

Очень очень sorry Годик где то смотрю лифаксапа, может чуть меньше, но так и не поняла кто Виолетта для него Сестра? Девушка? Подруга? @leafxupcf | send take

💘86

Signed лификсап тейки

25 Jul 2026, 11:36 UTC422 views13 reactionsread 8 August 2026
Video

А помните лефиксап геншин снимал? @leafxupcf | send take

💘75🆒1

Signed лификсап тейки

25 Jul 2026, 11:31 UTC318 views15 reactionsread 8 August 2026

сделайте пж с лификсапом гача реакции как с валерой гостером🥺 @leafxupcf | send take

9🌚3custom 53055689088607388212custom 59948184401147368411

Signed лификсап тейки

20 Jul 2026, 17:21 UTC339 views28 reactionsread 8 August 2026
Photo

хыхыхыхыхыхы @milkshwiwho @leafxupcf | send take

custom 599681789341991245016custom 59948184401147368417custom 599672691312768156541

Signed лификсап тейки

20 Jul 2026, 11:51 UTC336 views25 reactionsread 8 August 2026
Photo

После этого арта мне заблокировали акк в тт Тгк:Ало крис? @kristallxyesos @leafxupcf | send take

16❤‍🔥6custom 59968178934199124502💘1

Signed лификсап тейки

20 Jul 2026, 11:48 UTC307 views17 reactionsread 8 August 2026
Photo

Лификсап записал ролик по Майнкрафту Да ну нахуй я не верю Тгк:Ало крис? @kristallxyesos @leafxupcf | send take

💘105custom 59968178934199124502

Signed лификсап тейки

20 Jul 2026, 10:04 UTC265 views14 reactionsread 8 August 2026
Photo

Л*ификсаппп.. ьыьь., @leafxupcf | send take

8💘51

Signed лификсап тейки

Showing the 12 most recent of 19 posts we hold for @Leafxupcf. 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 — 929,086 of 1,169,250entries 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.

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

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

“leafxup confession” (@Leafxupcf), 508 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Leafxupcf.

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.