Channel
@lynxrecos
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
153subscribers
+16 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001864655599 |
|---|---|
| Type | Channel |
| Username | @lynxrecos |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 2 times, most recently 17 September 2026 |
| On Telegram | t.me/lynxrecos |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 22:37 | 153 | +3 |
| 31 Aug 2026, 10:25 | 150 | +6 |
| 25 Aug 2026, 04:25 | 144 | +2 |
| 17 Aug 2026, 17:54 | 142 | +5 |
| 9 Aug 2026, 19:31 | 137 | no change |
| 9 Aug 2026, 06:46 | 137 | first reading |
10 posts held, back to 18 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 10 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
196 reactions across 10 posts, in 17 distinct kinds. The most used accounts for 25.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5235736120767032242 | 49 | 25.0% | |
| custom 5359723644689850384 | 26 | 13.3% | |
| custom 5280530349036680059 | 25 | 12.8% | |
| custom 5199934196805557507 | 21 | 10.7% | |
| custom 5283214329934528501 | 10 | 5.10% | |
| custom 5339166397907901792 | 10 | 5.10% | |
| custom 5381810015793356561 | 9 | 4.59% | |
| 💘 | 8 | 4.08% | |
| custom 5253856570608988517 | 7 | 3.57% | |
| custom 5393353161308152795 | 7 | 3.57% | |
| 🔥 | 7 | 3.57% | |
| ❤ | 6 | 3.06% | |
| custom 5348222061573592152 | 3 | 1.53% | |
| 😇 | 3 | 1.53% | |
| 🥰 | 3 | 1.53% | |
| custom 5339305907035610291 | 1 | 0.51% | |
| custom 5469648363353834884 | 1 | 0.51% |
Custom emoji. 12 of the rows above are 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 10 of the 10 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 196 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 18 July 2026 to 7 August 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.
🙂🙂🙂🙂🙂 🤩🤩🤩🤩 🙂🙂🙂🙂🙂 🙂🙂🙂🙂🙂 🤩🤩 🙂🙂🙂🙂🙂 🙂🙂🙂🙂🙂 🤩🤩🤩
custom 53391663979079017929custom 51999341968055575075custom 52805303490366800595❤2custom 52357361207670322422custom 52832143299345285011custom 53597236446898503841
🌟🌟🌟🌟🌟 🌟🌟🌟🌟🌟 вот это мы 🌟🌟🌟🌟🌟 короче на даче 🌟🌟🌟 да. 🌟🌟 милашки с фото слева направо!!! Дана, Лиза, Даша, Даша, Настя, Ира, Аня 🤩
custom 523573612076703224211custom 53597236446898503846custom 51999341968055575074custom 52832143299345285013❤1custom 53933531613081527951
Video message, posted without a caption
custom 52805303490366800599custom 52357361207670322426custom 52832143299345285013custom 53482220615735921522
кто хочет в волейбол? завтра вечером, хз где пока, но компания исключительно добрых людей!!!! 🙂🙂🙂
custom 52357361207670322424❤3custom 53391663979079017921custom 53482220615735921521
⭐️⭐️ ⭐️⭐️
🥰3custom 53933531613081527953custom 52805303490366800592
⭐️🅰️🅰️🅰️🅰️🅰️🅰️🅰️🅰️🅰️ ⭐️⭐️🤩🤩🌟🌟🌟⭐️⭐️ ⭐️⭐️🤩🤩🌟🌟 ⭐️⭐️
custom 535972364468985038411custom 52357361207670322427custom 51999341968055575076custom 52832143299345285013💘1
Video message, posted without a caption
custom 52357361207670322426custom 53597236446898503843custom 53933531613081527952
🥀🥀 🥀🥀 🌟🌟🌟🌟🌟🌟🌟🌟 🤩 🥀🥀 🥀🥀 🥀🥀
custom 523573612076703224212custom 51999341968055575075custom 53597236446898503844
🤍🤍🤍🤍🌟🌟🌟🤍🤍🤍🤍 «𝐈𝐭'𝐬 𝐚 𝐩𝐢𝐭𝐲 𝐲𝐨𝐮 𝐰𝐞𝐫𝐞𝐧'𝐭 𝐬𝐜𝐚𝐫𝐞𝐝, 𝐢𝐭'𝐬 𝐬𝐨 𝐛𝐨𝐫𝐢𝐧𝐠» 🌟🌟
custom 53818100157933565619custom 52538565706089885177custom 52805303490366800596💘3
🌟🌟🌟🌟 🌟🌟🌟🌟 🌟🌟🌟🌟 🌟🌟🌟🌟🌟Внутри мы также прекрасны, 🌟🌟 как и снаружи 🌟🌟 🌟🌟 Зера🌟🌟
🔥7💘4😇3custom 52805303490366800593custom 51999341968055575071custom 52357361207670322421custom 53393059070356102911custom 53597236446898503841
Showing the 10 most recent of 10 posts we hold for @lynxrecos. 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.
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“𓌹♰darlynxxx♰𓌺” (@lynxrecos), 153 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/lynxrecos.
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.