Channel
@yite_mobile
On this record: Topic · Growth · Engagement · Posts · Cite this entry
27subscribers
+4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002673629437 |
|---|---|
| Type | Channel |
| Username | @yite_mobile |
| Created | Between 1 March 2025 and 11 May 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 2 October 2026 |
| On Telegram | t.me/yite_mobile |
Other / unclassifiable — 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 30 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 15:01 | 27 | +1 |
| 30 Aug 2026, 07:13 | 26 | +2 |
| 23 Aug 2026, 04:27 | 24 | +1 |
| 11 Aug 2026, 11:48 | 23 | no change |
| 7 Aug 2026, 16:01 | 23 | first reading |
16 posts held, back to 11 May 2025 — 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 16 posts for this entry, the most recent from 27 April 2026. An engagement rate over an empty window would be a number about nothing.
https://www.tiktok.com/@yitemobilejimma/video/7633488861045312776?_r=1&u_code=e0idmj1adj7ke1&preview_pb=0&sharer_language=en&_d=f32b2md1migg4a&share_item_id=7633488861045312776&source=h5_m×tamp=1777313019&user_id=7074239305640313857&sec_user_id=MS4wLjABAAAA2oYoODk2sFeWXoOgIC0bcPXmFOG6tCM82yxSYZKirqyfYDgymdSAhJYGekHo9YbF&item_author_type=1&social_share_type=0&utm_source=telegram&utm_campaign=client_share&utm_medi…
https://vt.tiktok.com/ZSHkaNUd4/
https://vt.tiktok.com/ZSHkyrxPK/
https://vm.tiktok.com/ZMDFvAyj1/
https://vm.tiktok.com/ZMH7nn86hweDr-D5bIZ/ This post is shared via TikTok Lite. Download TikTok Lite to enjoy more posts: https://www.tiktok.com/tiktoklite
https://vm.tiktok.com/ZMH7eu5vsQByq-2urgZ/ This post is shared via TikTok Lite. Download TikTok Lite to enjoy more posts: https://www.tiktok.com/tiktoklite
https://vm.tiktok.com/ZMSUHxvfP/
https://vm.tiktok.com/ZMSSrTuu5/
https://vm.tiktok.com/ZMSSrW4fu/
https://vm.tiktok.com/ZMSM3khjG/
Itel a18 Power ic repairing success
https://vm.tiktok.com/ZMS6p4GQv/
Showing the 12 most recent of 16 posts we hold for @yite_mobile. 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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“Yite mobile” (@yite_mobile), 27 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/yite_mobile.
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.