Telegram RegisterThe public register of Telegram
Telegram profile photo for ღ 𝑳𝒆𝒗𝒊𝒕𝒕𝒂𝒛𝒆 ღ

Channel

ღ 𝑳𝒆𝒗𝒊𝒕𝒕𝒂𝒛𝒆 ღ

@Levittazeofficial

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

612subscribers

+23 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-1002229382892
TypeChannel
Username@Levittazeofficial
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 8 October 2026
On Telegramt.me/Levittazeofficial

Topic

Personal blog — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 20 September 2026 and assigned it the closest of 31 fixed categories, at 70% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

589612600.57 August 2026 — 589 subscribers8 August 2026 — 589 subscribers15 August 2026 — 590 subscribers22 August 2026 — 596 subscribers29 August 2026 — 606 subscribers5 September 2026 — 607 subscribers28 September 2026 — 609 subscribers8 October 2026 — 612 subscribers7 August 20268 October 2026
8 measurements spanning 62 days, net +23. 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 586–615 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Oct 2026, 17:36612+3
28 Sept 2026, 04:56609+2
5 Sept 2026, 12:00607+1
29 Aug 2026, 00:56606+10
22 Aug 2026, 17:14596+6
15 Aug 2026, 20:04590+1
8 Aug 2026, 03:18589no change
7 Aug 2026, 14:52589first reading

Engagement

15 posts held, back to 2 August 2026 — 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 page of 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 15 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 19s
Average length
20s

Measured directly from 4 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

607 reactions across 15 posts, in 7 distinct kinds. The most used accounts for 24.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 538856229279316694015024.7%
🔥14824.4%
🍓10717.6%
custom 51973868388173882669515.7%
custom 59655426974846876106210.2%
custom 4992768747090477636437.08%
💯20.329%

Custom emoji. 4 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 are Telegram’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 15 of the 15 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 607 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 2 August 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.

Telegram Stars

Stars received
2
across the posts below
Posts paid on
2
of 15 we hold a reading for · 13%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Levittazeofficial. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 15 most recent posts we hold for this entry, published 2 August 2026 to 7 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

7 Aug 2026, 09:55 UTC136 views34 reactionsread 8 August 2026
Video

Чуть-чуть умерла 🩶

🔥27custom 53885622927931669405🍓2

7 Aug 2026, 09:55 UTC134 views24 reactionsread 8 August 2026
Video

this, that, this, that ⚡️

custom 519738683881738826616custom 53885622927931669407custom 49927687470904776361

7 Aug 2026, 05:22 UTC147 views35 reactionsread 8 August 2026
Photo

Какие офигенные образы 🤤

custom 519738683881738826629custom 59655426974846876104🍓1custom 53885622927931669401

7 Aug 2026, 05:16 UTC158 views31 reactionsread 8 August 2026
Photo

Няяяяяя ☺️🥹

custom 596554269748468761023custom 53885622927931669406💯2

7 Aug 2026, 05:16 UTC147 views32 reactionsread 8 August 2026
Photo

Капучино или американо? ☕

custom 499276874709047763621custom 53885622927931669409custom 51973868388173882662

7 Aug 2026, 05:14 UTC149 views35 reactions1 Starread 8 August 2026
Photo

Это официально офигительный камбэк 😛

custom 538856229279316694025🔥8custom 59655426974846876102

6 Aug 2026, 11:39 UTC200 views44 reactionsread 8 August 2026
Video

Джиниретик и ббокари 🤩🤩 cr :: sunamonto_stay

custom 538856229279316694028custom 51973868388173882668custom 49927687470904776367🍓1

6 Aug 2026, 07:26 UTC195 views50 reactionsread 8 August 2026
Photo

Ты что творишь? 🤯 Минус фандом........

🔥38🍓6custom 53885622927931669403custom 49927687470904776362custom 51973868388173882661

6 Aug 2026, 06:48 UTC191 views54 reactionsread 8 August 2026
Photo

Стиляги 💜💜💜

custom 538856229279316694040custom 59655426974846876106custom 51973868388173882664🍓3custom 49927687470904776361

6 Aug 2026, 06:48 UTC182 views44 reactionsread 8 August 2026
Photo

Внимание! Красный Минхо ❤️

🔥28🍓10custom 59655426974846876104custom 49927687470904776362

4 Aug 2026, 13:59 UTC213 views53 reactionsread 8 August 2026
Video

▫️ 👀: Я заболел, потому что Хан поцеловал меня, пока я спал! р.s. они даже не стесняются! 😁🤍 ▫️

🍓37🔥9custom 49927687470904776364custom 53885622927931669403

3 Aug 2026, 12:27 UTC244 views51 reactionsread 8 August 2026
Photo

Нежный цветочный ангел 💋

custom 519738683881738826631custom 538856229279316694010custom 59655426974846876107🍓2custom 49927687470904776361

Showing the 12 most recent of 15 posts we hold for @Levittazeofficial. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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

“ღ 𝑳𝒆𝒗𝒊𝒕𝒕𝒂𝒛𝒆 ღ” (@Levittazeofficial), 612 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/Levittazeofficial.

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.