Channel
@Lyambda_Port
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
29subscribers
+0 since we began measuring on 12 November 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004440154036 |
|---|---|
| Type | Channel |
| Username | @Lyambda_Port |
| Description | 🐉 ᥕᥱᥣᥴ𐔖ⲙᥱ t𐔖 ᥣ𐔤ᥲⲙbᦔᥲ'᥉ ρ𐔖rt! ————–—–——— ᥒρυⲃᥱⲧ! ⲙᥱⲏя ⳅ𐔖ⲃ𐔤ⲧ ᥈яⲙⳝⲇᥲ | {᥉hᥱ/hᥱr} ᦔᥱ᥉ιⳋᥒᥱr | |
| First recorded | 12 November 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Lyambda_Port |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Nov 2026, 01:22 | 29 | no change |
| 12 Nov 2026, 00:47 | 29 | first reading |
15 posts held, back to 12 September 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.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 7 of 8 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 November 2026 |
|---|---|
| Posts held | 15 (12 September 2026 – 11 November 2026) |
| Views total | 293 |
| Reactions total | 34 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Nov 2026, 01:22 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 12 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
49 reactions across 10 posts, in 17 distinct kinds. The most used accounts for 18.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🍾 | 9 | 18.4% | |
| custom 5215461040451513797 | 5 | 10.2% | |
| custom 5219704377945660748 | 5 | 10.2% | |
| custom 5366071236986178267 | 4 | 8.16% | |
| custom 5413422173387780304 | 3 | 6.12% | |
| 👻 | 3 | 6.12% | |
| 💅 | 3 | 6.12% | |
| 🕊 | 3 | 6.12% | |
| 🥰 | 3 | 6.12% | |
| ❤ | 2 | 4.08% | |
| 🆒 | 2 | 4.08% | |
| 👾 | 2 | 4.08% | |
| custom 5219804330424572273 | 1 | 2.04% | |
| 🍓 | 1 | 2.04% | |
| 🎄 | 1 | 2.04% | |
| 👀 | 1 | 2.04% | |
| 💋 | 1 | 2.04% |
Custom emoji. 5 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 15 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 49 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 12 September 2026 to 11 November 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.
Telegram’s own ‘edited’ marker: 1 of 10 posts held from the last 30 days (10.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Всем привет, с вами Лямбда и я планирую Нью эру, которая (надеюсь) продлиться долго🌟 Пока что попробуйте угадать перса😳 Подсказка: этот персонаж из аниме и его имя начинается на "М" 💙💙💙💙💙💙💙💙 #sp
custom 52154610404515137973👀1custom 54134221733877803041
Posted without readable text
Posted without readable text
custom 52197043779456607482🎄1custom 52154610404515137971custom 54134221733877803041
Posted without readable text
custom 53660712369861782674👻1custom 52154610404515137971custom 52197043779456607481custom 54134221733877803041
꧁𝕷𝖞𝖆𝖒𝖇𝖉𝖆/ⲗяⲙⳝⲇⲁ 𝕻𝖔𝖗𝖙꧂ pinned a photo
File, posted without a caption
🍾2👻1
✦ 🪪 𝘄𝗲𝗹𝗰𝗼𝗺𝗲 𝘁𝗼 𝗹𝘆𝗮𝗺𝗯𝗱𝗮'𝘀 𝗽𝗼𝗿𝘁! ⟡ 🪷 • ᥒρυⲃᥱⲧ! ⲙᥱⲏя ⳅ𐔖ⲃ𐔤ⲧ ᥈яⲙⳝⲇᥲ | {᥉hᥱ/hᥱr} ᦔᥱ᥉ιⳋᥒᥱr |! 🐉 ─── ⲏⲁⲃυⲅⲁⳡυя ─── 🐉 • ⟡ ⲡⲣⲁύⲥ • ⟡ ⲧυⲕ ⲧⲟⲕ • ⟡ ⲟⲧⳅыⲃы • ⟡ ⲁⲏⲟⲏ ✦ tags: #Order #Banner #Pfp #Practice #Repost #Important #sp
🍾1🕊1custom 52197043779456607481
꧁𝕷𝖞𝖆𝖒𝖇𝖉𝖆/ⲗяⲙⳝⲇⲁ 𝕻𝖔𝖗𝖙꧂ pinned Deleted message
🐉 ✦ 𝗿𝗲𝘃𝗶𝗲𝘄𝘀 ✦ 📜 • под этим постом вы можете поделиться своим мнением о выполнении заказа и моей работе! 🪞 • буду очень рада любому фидбеку в комментариях, это помогает мне расти как дизайнеру (≧▽≦) 🫧 • ваше мнение очень важно для меня! 🧪 ✦ ⟡ ✦
🍾2🆒2🕊1custom 52197043779456607481
🪷 ✦ 𝗽𝗿𝗶𝘀𝗲| прайс ⟡ 🧪 📜 ⳝⲁⲏⲏⲉⲣы: • 1 баннер — 15★ • 2-3 баннеров — 25★ • 4-5 баннеров — 50★ ⟡ далее по договорной цене 🪞ⲁⲃⲁⲧⲁⲣⲕυ: • 1 аватарка — бесплатно • 2-3 аватарки — 15★ • 4-5 аватарок — 25★ ⟡ далее по договорной цене ⚙️ заказ вне очереди: 25★ ✦ буду очень рада чаевым ✦ 📜 анкета для заказа ниже! ⲁⲏⲕⲉⲧⲁ ⲇⲗя ⳅⲁⲕⲁⳅⲁ! 1) Баннер/Аватарка 2) Количество 3)Имя персонажа и его фд 4) Текст (в моно) 5) Ц…
🍾1👻1🕊1custom 52198043304245722731
꧁вышло новое видео!꧂ 🎆 его можно посмотреть в тик токе
💅2🍾1🥰1
Всем новым подписчикам привет! Я начинающий дизайнер и можете звать меня Лямбдой! Тут я делаю баннеры и авы на заказ, так что тут будет интересно🔮
❤1🍓1🍾1💅1🥰1
Showing the 12 most recent of 15 posts we hold for @Lyambda_Port. 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 1 registered channel — 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.
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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“꧁𝕷𝖞𝖆𝖒𝖇𝖉𝖆/ⲗяⲙⳝⲇⲁ 𝕻𝖔𝖗𝖙꧂” (@Lyambda_Port), 29 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/Lyambda_Port.
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.