20 Mar 2024, 06:28 UTC276 viewsread 8 August 2026
Unboxing de la alarma sin cuotas de Aliexpres!!! https://youtu.be/bcjokV0M39w?si=ppeiELLhAT0gYyVC
Channel
Yustify
@yustifygee
On this record: Growth · Engagement · Posts · Citations · Cite this entry
345subscribers
-4 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 | -1001401003000 |
|---|---|
| Type | Channel |
| Username | @yustifygee |
| Created | Between 1 August 2018 and 30 November 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 10 September 2026 |
| On Telegram | t.me/yustifygee |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 04:25 | 345 | -2 |
| 24 Aug 2026, 13:39 | 347 | -1 |
| 16 Aug 2026, 18:23 | 348 | -1 |
| 8 Aug 2026, 06:49 | 349 | no change |
| 7 Aug 2026, 22:49 | 349 | first reading |
Engagement
6 posts held, back to 28 February 2024 — 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 6 posts for this entry, the most recent from 20 March 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
20 Mar 2024, 06:28 UTC268 viewsread 8 August 2026
Este canal dejará de estar activo, nos pasamos a t.me/yustifygeek
28 Feb 2024, 16:19 UTCviews —
Channel photo removed
28 Feb 2024, 16:16 UTC429 viewsread 8 August 2026
Este canal dejará de estar activo, nos pasamos a t.me/yustifygeek
28 Feb 2024, 16:13 UTCviews —
Channel name was changed to «Yustify»
28 Feb 2024, 16:13 UTCviews —
Channel name was changed to «Yustif»
Showing the 6 most recent of 6 posts we hold for @yustifygee. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“Yustify” (@yustifygee), 345 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/yustifygee.
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.