Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝑳𝑼𝑵𝑬ᵖᵒʳᵗ

Channel

𝑳𝑼𝑵𝑬ᵖᵒʳᵗ

@lunee_portfolio

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

39subscribers

-8 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004290073096
TypeChannel
Username@lunee_portfolio
Created1 July 2026 — measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live10 October 2026
Measurements held9
Confirmed unchanged1 time, most recently 10 October 2026
On Telegramt.me/lunee_portfolio

Topic

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 29 September 2026 and assigned it the closest of 31 fixed categories, at 71% 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.

Growth

3947438 August 2026 — 47 subscribers10 August 2026 — 47 subscribers16 August 2026 — 43 subscribers23 August 2026 — 42 subscribers30 August 2026 — 45 subscribers9 September 2026 — 44 subscribers17 September 2026 — 43 subscribers30 September 2026 — 41 subscribers10 October 2026 — 39 subscribers8 August 202610 October 2026
9 measurements spanning 62 days, net -8. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 38–48 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Oct 2026, 06:3939-2
30 Sept 2026, 10:2141-2
17 Sept 2026, 00:3843-1
9 Sept 2026, 03:4144-1
30 Aug 2026, 18:4445+3
23 Aug 2026, 05:1942-1
16 Aug 2026, 06:5443-4
10 Aug 2026, 13:3147no change
8 Aug 2026, 18:4947first reading

Engagement

13 posts held, back to 1 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 13 posts for this entry, the most recent from 26 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

166 reactions across 11 posts, in 26 distinct kinds. The most used accounts for 13.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2313.9%
❤2012.0%
custom 63141827421373753941810.8%
💘1810.8%
🕊159.04%
⚡116.63%
custom 631211703466669238484.82%
custom 631456858911434627484.82%
🍌63.61%
🌭53.01%
custom 631437180659774522242.41%
custom 631439231077161670342.41%
🍓42.41%
😡42.41%
❤‍🔥31.81%
🥰31.81%
custom 631225291025206853721.20%
custom 631451662001006547321.20%
custom 610467656101580334610.602%
custom 631415146618552724510.602%
6 further kinds63.61%

Custom emoji. 9 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 11 of the 13 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 166 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 1 July 2026 to 26 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

26 Jul 2026, 19:08 UTC61 views1 reactionsread 10 August 2026

поставьте классные реакции с котиками

⚡1

26 Jul 2026, 19:07 UTC61 views32 reactionsread 10 August 2026

螢 𝑁𝐸𝑊 𝑃𝑂𝑆𝑇 𓎟‌𓎟 ˢʰᵉ › ʰᵉʳ ⚔ ⌒꯭‌⌒꯭ֺ⌒ #баннер ⏜‌᪾ᷓ𐑼 ꒰‌ ㅤ܃🪷᷼ ‌ۢ. ﹫ℒ𝑢𝑛𝑒 PORT૮₍ ´ ᩙ ˋू₎ა ㅤㅤ‌ ⏝ֽ۠۠֯kִ𑄜ⲙⲙᧉ‌нׄⲧ𐐼թꭎׄύ: в комментариях файл в хорошем качестве _ ᴘʀɪᴄᴇ ⏝ֽ۠۠〬︶፝֟ ⇉𝐀𝗎𝗍.𝖍𝗈𝗋⇊ ﹫𝗌𝗐𝖾𝖾𝗍 @Saw_wwako ᅠ — ࣪ ׅ ִ 𓇿 . ֹ _ ࣪ ׅ ִ

custom 631418274213737539411custom 63145685891143462747custom 63121170346666923846custom 63122529102520685372custom 63143718065977452222custom 63143923107716167032custom 63145166200100654732

13 Jul 2026, 09:42 UTC197 views28 reactionsread 10 August 2026
Photo

螢 𝑁𝐸𝑊 𝑃𝑂𝑆𝑇 𓎟‌𓎟 ˢʰᵉ › ʰᵉʳ ⚔ ⌒꯭‌⌒꯭ֺ⌒ #баннер ⏜‌᪾ᷓ𐑼 ꒰‌ ㅤ܃🪷᷼ ‌ۢ. ﹫ℒ𝑢𝑛𝑒 PORT૮₍ ´ ᩙ ˋू₎ა ㅤㅤ‌ ⏝ֽ۠۠֯kִ𑄜ⲙⲙᧉ‌нׄⲧ𐐼թꭎׄύ: в комментариях файл в хорошем качестве _ ᴘʀɪᴄᴇ ⏝ֽ۠۠〬︶፝֟ ⇉𝐀𝗎𝗍.𝖍𝗈𝗋⇊ ﹫𝗌𝗐𝖾𝖾𝗍 @Saw_wwako ᅠ — ࣪ ׅ ִ 𓇿 . ֹ _ ࣪ ׅ ִ

custom 63141827421373753946⚡5🔥5😡4❤3custom 63121170346666923842custom 63141514661855272451custom 63143923107716167031

11 Jul 2026, 13:48 UTC211 views16 reactionsread 10 August 2026
Photo

螢 𝑁𝐸𝑊 𝑃𝑂𝑆𝑇 𓎟‌𓎟 ˢʰᵉ › ʰᵉʳ ⚔ ⌒꯭‌⌒꯭ֺ⌒ #баннер #заказ ⏜‌᪾ᷓ𐑼 ꒰‌ ㅤ܃🪷᷼ ‌ۢ. ﹫ℒ𝑢𝑛𝑒 PORT૮₍ ´ ᩙ ˋू₎ა ㅤㅤ‌ ⏝ֽ۠۠֯kִ𑄜ⲙⲙᧉ‌нׄⲧ𐐼թꭎׄύ: у меня классные заказчики а еще я усталь_ ᴘʀɪᴄᴇ ⏝ֽ۠۠〬︶፝֟ ⇉𝐀𝗎𝗍.𝖍𝗈𝗋⇊ ﹫𝗌𝗐𝖾𝖾𝗍 @Saw_wwako ᅠ — ࣪ ׅ ִ 𓇿 . ֹ _ ࣪ ׅ ִ

🌭4🔥4🕊4💘2⚡1custom 63143718065977452221

10 Jul 2026, 14:50 UTC193 views24 reactionsread 10 August 2026
Photo

new post @lunee_portfolio tags : #баннер customer: O⁠_⁠o creator : @Saw_wwako time: 1 час 18 минут

🍌6💘5🕊4🔥3⚡1🌚1🌭1👍1

7 Jul 2026, 17:52 UTC244 views14 reactionsread 10 August 2026
Photo

new post @lunee_portfolio tags : #аватарка customer: O⁠_⁠o creator : @Saw_wwako time: 1 час в комментариях в нормальном качестве

🔥5❤3🕊3💘2⚡1

7 Jul 2026, 11:54 UTC206 views8 reactionsread 10 August 2026
Photo

new post @lunee_portfolio tags : #баннер customer: O⁠_⁠o creator : @Saw_wwako time: 1 час 9 минут в комментариях в нормальном качестве

❤3⚡2🔥2🕊1

5 Jul 2026, 21:41 UTC235 views14 reactionsread 10 August 2026
Photo

new post @lunee_portfolio tags : #баннер customer: O⁠_⁠o creator : @Saw_wwako time: 27 минут в комментариях в нормальном качестве легкая работа

❤5🍓4💘4🕊1

4 Jul 2026, 20:24 UTC221 views7 reactionsread 10 August 2026
File

new post @lunee_portfolio tags : #аватарка customer: O⁠_⁠o creator : @Saw_wwako time: 2 часа 11 минут в файле потому что без файла тг делает очеееень плохое качество

❤2💋1💘1🔥1🕊1🥰1

1 Jul 2026, 15:10 UTC237 views5 reactionsread 10 August 2026
Photo

𝙉𝘦𝑾 𝗽𝗼𝘀𝘁 — 𝑳𝑼𝑵𝑬ᵖᵒʳᵗ . . ᴛᴀɢs — #баннер . . 🎏 バラ

❤‍🔥3💘2

1 Jul 2026, 10:10 UTC≈1,950 views17 reactionsread 10 August 2026
Photo

𓂂 𓎟𓎟 ִ ✶ 𝐍𝖆𝐯𝐢𝖌𝖆𝐭𝐢𝖔𝐧 ׄ ⇊ ִ╮ 𓂂 ִ ◞†◟ ⇉𝐇авиг𝓪ция с𑄝‌здᴀна для удσбного υ бы𝓬ꭑ‌р𑄝‌г𑄝‌ п𑄝‌иска нվжн𑄝‌й вɑׁׅм инф𑄝‌թм𝓪ции. ╵🗡️╵𝐤𝗂𝗌𝗌 𝐦𝖾 ⎯⎯⎯ ɯꫝꪖƚ?? ⎯⎯⎯ 𝐬𝗁𝖾 - 𝐡𝖾𝗋 . .   ٬٬ 〣 Важно ୖ Анкета 𓎟 вп пост ⊰⁠⊹ฺ прайс/цена ╰── ﴿ @Lune ﴾ ׅ ׁ ﹙˓ 🎥 ˒﹚: հҽհҽ ───╮ #баннер #аватарка #заказ ❞ へ ??𑄾 отзывы!

❤4🔥3💘2💔1🕊1🥰1🥴1😭1

Showing the 12 most recent of 13 posts we hold for @lunee_portfolio. 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.

Mentions

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.

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.

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 10 October 2026 — this entry's latest reading, not the date you are reading this.

“𝑳𝑼𝑵𝑬ᵖᵒʳᵗ” (@lunee_portfolio), 39 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/lunee_portfolio.

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.