Telegram RegisterThe public register of Telegram
Telegram profile photo for Olivia

Channel

Olivia

@olivess

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

337subscribers

+0 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-1001474229401
TypeChannel
Username@olivess
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 September 2026
Measurements held6
Confirmed unchanged2 times, most recently 17 September 2026
On Telegramt.me/olivess

Topic

Technology — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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

3373413397 August 2026 — 337 subscribers8 August 2026 — 337 subscribers16 August 2026 — 339 subscribers24 August 2026 — 340 subscribers30 August 2026 — 341 subscribers9 September 2026 — 337 subscribers7 August 20269 September 2026
6 measurements spanning 33 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 336–342 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 05:55337-4
30 Aug 2026, 17:08341+1
24 Aug 2026, 02:44340+1
16 Aug 2026, 17:08339+2
8 Aug 2026, 01:38337no change
7 Aug 2026, 04:17337first reading

Engagement

20 posts held, back to 8 September 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 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 20 posts for this entry, the most recent from 10 November 2023. An engagement rate over an empty window would be a number about nothing.

Reaction mix

294 reactions across 19 posts, in 14 distinct kinds. The most used accounts for 41.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍12341.8%
😢4816.3%
🔥4113.9%
🎉186.12%
❤175.78%
🥰155.10%
👏113.74%
💔62.04%
😁51.70%
😭41.36%
🕊20.68%
😱20.68%
💋10.34%
🤨10.34%

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 19 of the 20 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 294 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 8 September 2022 to 10 November 2023, 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

10 Nov 2023, 18:42 UTC≈3,240 views15 reactionsread 7 August 2026
Photo

Photo, posted without a caption

💔6👏4👍2🔥1🕊1🤨1

Signed ꦄꦏꦶꦆ

11 May 2023, 11:26 UTC≈4,900 views66 reactionsread 7 August 2026
Photo

Goodbye Xiaomi

😢48👍9😁3😭3🎉1👏1🕊1

Signed アクマ

10 Mar 2023, 18:24 UTC≈5,400 views4 reactionsread 7 August 2026
File

File, posted without a caption

🔥3👍1

Signed アクマ

10 Mar 2023, 18:19 UTC≈5,530 views28 reactionsread 7 August 2026
Photo

🛠ꦄꦏꦶꦆ #A10 #Olives #Vanilla #Redmi 8/8A/8A Dual | Nusantara Project EOL| Port | Android 10 🗒 Notes: • This Port Rom from Santoni • Vanilla Build • Use magisk delta for CTS pass, flash modul safety net then enable zygisk • Clean flash mandatory • permissive Build 🐞Known Issue:??? 📲 Installation: • Wipe system, vendor, data, cache, dalvik • Flash rom • Flash Gapps • Format data • Flash magisk if want root • Reboot …

🔥14👍12❤1💋1

Signed toolkit

8 Mar 2023, 15:20 UTC≈4,750 views11 reactionsread 7 August 2026
Photo

🛠ꦄꦏꦶꦆ #A11 #Olives #Gapps #Redmi 8/8A/8A Dual XDroidOs 1.5| Port | Android 11 🗒 Notes: • This Port Rom from Whyred • Gapps Build •Use magisk for CTS pass • Clean flash mandatory • permissive Build 🐞Known Issue:??? 📲 Installation: • Wipe system, vendor, data, cache, dalvik • Flash rom • Format data • Flash magisk if want root • Reboot & enjoy 🎉 Credits Thanks to ??? for rom 🏷 @Redmi8AIndonesia 🏷 @Redmi8ID_Group

👍10🔥1

Signed toolkit

23 Feb 2023, 17:13 UTC≈3,990 views15 reactionsread 7 August 2026
Photo

🛠ꦄꦏꦶꦆ #A10 #Olives #Vanilla #Redmi 8/8A/8A Dual BlissOs | Port | Android 10 🗒 Notes: • This Port Rom from Whyred • Vanilla Build •Use magisk for CTS pass • Clean flash mandatory • Enforce Build 🐞Known Issue:??? 📲 Installation: • Wipe system, vendor, data, cache, dalvik • Flash rom • Flash Gapps • Format data • Flash magisk if want root • Reboot & enjoy 🎉 Credits Thanks to ayan for rom 🏷 @Redmi8AIndonesia 🏷 @Red…

👍7❤6😁2

Signed toolkit

23 Feb 2023, 16:06 UTC≈3,690 views10 reactionsread 7 August 2026
Photo

🛠ꦄꦏꦶꦆ #A10 #Olives #Gapps #Redmi 8/8A/8A Dual Paranoid | Port | Android 10 🗒 Notes: • This Port Rom from Whyred • Gapps Build • Use magisk for CTS pass • Clean flash mandatory • Enforce Build 🐞Known Issue:??? 📲 Installation: • Wipe system, vendor, data, cache, dalvik • Flash rom • Format data • Flash magisk if want root • Reboot & enjoy 🎉 Credits Thanks to keerten for rom 🏷 @Redmi8AIndonesia 🏷 @Redmi8ID_Group

👍4🔥4👏1😭1

Signed toolkit

30 Dec 2022, 16:00 UTC≈4,380 views25 reactionsread 7 August 2026
Photo

🛠ꦄꦏꦶꦆ #A10 #Olives #Vanilla #Redmi 8/8A/8A Dual Nusantara Project LTS | Port | Android 10 🗒 Notes: • This Port Rom from Whyred • Vanilla Build • CTS pass by default in olivelite i don't know in olive & wood • Clean flash mandatory • Enforce Build 📲 Installation: • Wipe system, vendor, data, cache, dalvik • Flash rom • Flash GApps • Format data • Flash magisk if want root • Reboot & enjoy 🎉 Credit: Thanks to i for…

👍18🥰6❤1

Signed toolkit

20 Dec 2022, 06:27 UTC≈4,240 views8 reactionsread 7 August 2026
File

Flash in magisk

🥰7👍1

Signed アクマ Off

13 Dec 2022, 07:40 UTC≈4,690 views15 reactionsread 7 August 2026
Photo

🛠ꦄꦏꦶꦆ #A10 #Olives #Vanilla #Redmi 8/8A/8A Dual Havoc V3.9 | Port | Android 10 🗒 Notes: • This Port Rom from Whyred • Vanilla Build • Permisive Build but don't worry you can change to enforce using xiaomiparts in setting • Use Magisk for Safetynet pass • Clean flash mandatory • Don't use F2Fs 🐞Known Issue: • ??? 📲 Installation: • Wipe system, vendor, data, cache, dalvik • Flash rom • Flash GApps • Format data • F…

👍10🔥4❤1

Signed toolkit

29 Nov 2022, 17:12 UTC≈3,990 views4 reactionsread 7 August 2026
File

If u facing bug cant active hotspot in qassa v2.1 flash this file via recovery

👍4

Signed アクマ Off

28 Nov 2022, 05:21 UTC≈4,060 views15 reactionsread 7 August 2026
Photo

🛠ꦄꦏꦶꦆ #A10 #Olives #Vanilla #Redmi 8/8A/8A Dual AOSP QASSA V2.1 | Port | Android 10 🗒 Notes: • This Port Rom from Whyred • Vanilla Build • Enforcing Build • Safetynet pass by default • Clean flash mandatory • Don't use F2Fs 🐞Known Issue: • ??? 📲 Installation: • Wipe system, vendor, data, cache, dalvik • Flash rom • Flash GApps • Format data • Flash magisk if want root • Reboot & enjoy 🎉 Credit: Thanks to Yuu_kih…

🎉8👍5😱2

Signed toolkit

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

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

“Olivia” (@olivess), 337 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/olivess.

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.