Telegram RegisterThe public register of Telegram
Telegram profile photo for archive 𝑜𝒻 bloomiė. ❀

Channel

archive 𝑜𝒻 bloomiė. ❀

@bloomiearchive

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

5subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003987539691
TypeChannel
Username@bloomiearchive
Created19 July 2026measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/bloomiearchive

Growth

56 August 2026 — 5 subscribers13 August 2026 — 5 subscribers6 August 202613 August 2026
2 measurements spanning 6 days. 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 4–6 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 00:165no change
6 Aug 2026, 21:015first reading

Engagement

11 posts held, back to 19 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
1267.5%
avg views ÷ 5 subscribers
Avg views / post
63.4
8 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
11
of 11 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 27 July 2026
Posts held11 (19 July 202627 July 2026)
Views total507
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 00: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

Links
1

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

24 Jul 2026, 10:55 UTC75 viewsread 13 August 2026

DI REJECT DI REJECT TERUS 📞... HADUH KENALA SIH SETIAP AKU CALL ATAU SMS SELALU DI REJECT JADI #KESEL 😡😡😡 ADUH KENAPSIH ??? PESANAN DAN TELEPON KAMU DI REJECT TERUSS ?? JANGAN KESEL DEHH MENDING COBA KALIAN KESINI DEH @frlaraa @frlaraa @frlaraa KARENA AKU JAMIN 1000% PESANAN KAMU ENGGA AKAN DI REJECT SINI DEH SEKALIAN MIMIN SPILL DISINI ADA APA AJA ( nokos teles , nokos wa teleprem , telestars, Netflix , Canva , me

23 Jul 2026, 15:53 UTC64 viewsread 13 August 2026

ㅤㅤㅤㅤㅤ ⤿ TESTIMONIALS 𐙚 𓂃 Bloomie Diary🪽 𝜗𝜚 if you've shopped at bloomie, we'd love to hear your experience. feel free to leave a sweet testimonial about our service and products. every little message means the world to us. thank you, pretty! 🩰🫧

23 Jul 2026, 15:51 UTC92 viewsread 13 August 2026

ㅤㅤㅤㅤㅤ ⤿ RATING & REVIEW 𐙚 🦩 Bloomie Diary 🫧 𝜗𝜚 please leave your honest rating and review after shopping with us. your sweet feedback helps bloomie grow and become a trusted little store. thank you for being here, pretty! 🎀🤍 100000/10 disini fast banget buat pengerjaan nya, dan kakak nya ramah banget. selain itu hasil dari custom disini sesuai sama apa yang aku mau ban

Showing the 11 most recent of 11 posts we hold for @bloomiearchive. 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 — 876,484 of 1,481,217entries 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 2 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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“archive 𝑜𝒻 bloomiė. ❀” (@bloomiearchive), 5 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/bloomiearchive.

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.