Мама попросила у меня телефон чтобы пофотографироваться😐😐

Channel
pretty girl avenue
@luvxmix
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
19subscribers
+2 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003705351106 |
|---|---|
| Type | Channel |
| Username | @luvxmix |
| Created | Between 1 February 2026 and 3 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 13 October 2026 |
| On Telegram | t.me/luvxmix |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Oct 2026, 08:51 | 19 | +1 |
| 23 Aug 2026, 11:55 | 18 | +1 |
| 11 Aug 2026, 20:46 | 17 | no change |
| 9 Aug 2026, 12:31 | 17 | first reading |
Engagement
7 posts held, back to 3 July 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 7 posts for this entry, the most recent from 12 July 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 21s
- Average length
- 11s
Measured directly from 2 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
16 reactions across 4 posts, in 6 distinct kinds. The most used accounts for 31.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5235894093959168803 | 5 | 31.3% | |
| custom 5443038081722654359 | 4 | 25.0% | |
| custom 5445014458168546281 | 3 | 18.8% | |
| custom 5442739860668457611 | 2 | 12.5% | |
| custom 5442917869883000875 | 1 | 6.25% | |
| custom 5443103176246989648 | 1 | 6.25% |
Custom emoji. Every row above is a 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 4 of the 7 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 16 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 3 July 2026 to 12 July 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.
Recent posts
в родном зажопинске🤪
custom 54430380817226543593custom 54450144581685462812
Обожаю свой директ в инсте 🙂😍
я объелась шашлыком 😐
custom 54427398606684576112custom 54429178698830008751custom 54450144581685462811
Мне подарили два букета цветов, а я завтра улетаю домой😐
custom 52358940939591688035
Этот год был невероятно тяжелым. Было очень много стресса Но я очень благодарна людям, которые меня окружали Спасибо мои прекрасным девочкам за то, что появились в моей жизни Просто самые прекрасные, лучшие дамы🩷🍬
custom 54430380817226543591custom 54431031762469896481
ПЕРВЫЙ КУРС ВСЕ🤪
Showing the 7 most recent of 7 posts we hold for @luvxmix. 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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“pretty girl avenue” (@luvxmix), 19 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/luvxmix.
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.