Telegram RegisterThe public register of Telegram
Telegram profile photo for Û° 𓄰. ࣧ ࣮𝓗𝑎𝑛𝑎𝑘𝑜'𝓌 𝓘𝑛 ࣮𝑓𝑜𝆹𝅥.˙𝆹[📋𝆩🌊]𓂅

Channel

Û° 𓄰. ࣧ ࣮𝓗𝑎𝑛𝑎𝑘𝑜'𝓌 𝓘𝑛 ࣮𝑓𝑜𝆹𝅥.˙𝆹[📋𝆩🌊]𓂅

@neuvillettessoulmate

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry

9subscribers

+0 since we began measuring on 15 August 2026

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

Register entry

Telegram ID-1002262036112
TypeChannel
Username@neuvillettessoulmate
Created28 January 2025 — measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live15 September 2026
Measurements held2
On Telegramt.me/neuvillettessoulmate

Growth

915 Aug 2026, 11:04 — 9 subscribers15 Aug 2026, 11:15 — 9 subscribers15 Aug 2026, 11:0415 Aug 2026, 11:15
2 measurements taken within a single day. 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 8–10 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 11:159no change
15 Aug 2026, 11:049first reading

Engagement

12 posts held, back to 28 January 2025 — 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 12 posts for this entry, the most recent from 17 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
6
Links
2

Lifetime counters from Telegram’s own channel header, read 15 August 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.

Reaction mix

238 reactions across 8 posts, in 10 distinct kinds. The most used accounts for 20.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52447524124675495944920.6%
custom 51977003843149164514619.3%
custom 53935327596605861974418.5%
custom 53797445789055947343916.4%
☃197.98%
🐳145.88%
🕊135.46%
🆒62.52%
❀‍🔥41.68%
🍓41.68%

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

Measured over the 12 most recent posts we hold, published 28 January 2025 to 17 May 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

17 May 2026, 18:49 UTC311 viewsread 15 August 2026

🌟🌟🌟

Signed Рест .𝅄۫☁ ࣧ .𝓗𝒶.𝑛𝑎𝓀𝑜.𔖳𓈒 ֺ𝓝𝑒𝓟𝓿.𝑖𝑙𝓵𝑒𝑡𝑡𝓮𝅄۫ ݁ #𝒩𝑒𝑢𝑣𝒟𝓁𝓁𝑒𝑡𝑡𝑒𝑠𝒲𝑖𝑓𝑒 gi @ МёвОхаМы каМПМ

17 May 2026, 18:48 UTC318 views24 reactionsread 15 August 2026
Photo

🀩🀩 ⇄ ֎🥹🥹 ÖŽÛªÖº . 🀩🥹 ֮⇊ 🥹 🌟 ðŸ€©àž±àž± 𝅥 𝄀 𝒎𝒐𝒖𝓇 𝒪𝒑𝒊𝒏𝒊𝒪𝒏 𝒶𝑏𝒪𝑢𝑡 𝓂𝒆 🌟ˎˊ˗ 🌟 . . . . . . • пр𝓊МОЌ𝒶ю люб𝒪е 𝒪бП𝒞МПв𝒶ММ𝒪е ЌМ𝑒МО𝑒. 🀩 🌟 ꯭

☃9🆒6🕊5🐳4

Signed Рест .𝅄۫☁ ࣧ .𝓗𝒶.𝑛𝑎𝓀𝑜.𔖳𓈒 ֺ𝓝𝑒𝓟𝓿.𝑖𝑙𝓵𝑒𝑡𝑡𝓮𝅄۫ ݁ #𝒩𝑒𝑢𝑣𝒟𝓁𝓁𝑒𝑡𝑡𝑒𝑠𝒲𝑖𝑓𝑒 gi @ МёвОхаМы каМПМ

17 May 2026, 18:30 UTC295 views0 reactionsread 15 August 2026

🌟🌟🌟

Signed Рест .𝅄۫☁ ࣧ .𝓗𝒶.𝑛𝑎𝓀𝑜.𔖳𓈒 ֺ𝓝𝑒𝓟𝓿.𝑖𝑙𝓵𝑒𝑡𝑡𝓮𝅄۫ ݁ #𝒩𝑒𝑢𝑣𝒟𝓁𝓁𝑒𝑡𝑡𝑒𝑠𝒲𝑖𝑓𝑒 gi @ МёвОхаМы каМПМ

17 May 2026, 18:30 UTC291 viewsread 15 August 2026

❀ ❀❀❀❀ ❀❀❀❀❀❀❀❀❀❀❀

Signed Рест .𝅄۫☁ ࣧ .𝓗𝒶.𝑛𝑎𝓀𝑜.𔖳𓈒 ֺ𝓝𝑒𝓟𝓿.𝑖𝑙𝓵𝑒𝑡𝑡𝓮𝅄۫ ݁ #𝒩𝑒𝑢𝑣𝒟𝓁𝓁𝑒𝑡𝑡𝑒𝑠𝒲𝑖𝑓𝑒 gi @ МёвОхаМы каМПМ

30 Dec 2025, 08:04 UTC975 views23 reactionsread 15 August 2026
Forwarded from @myfavs6Photo

❌❌❌🌟🌟🌟🌟🌟 🌟🌟【 НевОллет 】is @hanakoneuv's husband ! 🌟 ( #genshinimpact ) 


custom 53935327596605861978custom 51977003843149164515custom 52447524124675495945custom 53797445789055947345

Signed .𝅄۫🖇 ࣧ .𝓗𝒶.𝑛𝑎𝓀𝑜.𔖳𓈒 ֺ𝓝𝑒𝓟𝓿.𝑖𝑙𝓵𝑒𝑡𝑡𝓮𝅄۫ ݁ #𔖳𝑁eu𝑣illettes𝑊ife 𝅥 #𔖳𝑁euvi𝑙𝑙ette𝑘𝑖sser ࣧ gi mn @

16 Dec 2025, 17:20 UTC≈1,110 views28 reactionsread 15 August 2026

@neuvillettesgirlfriend ГскЌ ОМфП @neuvillettesamour КаМал Псхк с НёвОллетПЌ (Нег к ЎаблаЌ) https://t.me/+fer60B01myphZjMy Щп @neuvillettesprincess ПрПстП каМал https://t.me/+e_jCCMy0WMNmZjIy СайЎ @neuvillettesdear КЌЌ

custom 519770038431491645111custom 53797445789055947349custom 52447524124675495948

Signed .𝅄۫🖇 ࣧ .𝓗𝒶.𝑛𝑎𝓀𝑜.𔖳𓈒 ֺ𝓝𝑒𝓟𝓿.𝑖𝑙𝓵𝑒𝑡𝑡𝓮𝅄۫ ݁ [ ࣪ 𝑠𝒜𝑒 𝅥 𝒜.𝑒𝓇 ]◍⃘ ÛªÖŽ #𔖳𝑁eu𝑣illettes𝑊ife 𝅥 #𔖳𝑁euvi𝑙𝑙ette𝑘𝑖sser ࣧ gi @

4 Oct 2025, 06:02 UTC≈1,270 views32 reactionsread 15 August 2026
Poll

✚✚𝆹 𝆭 🀩🀩🀩🍭

  1. 🀩 🀩руг ï¿®11%
  2. 🀩 🀩МакПЌый ï¿®13%
  3. 🀩 🀩з ПЎМПгП флуЎа/рПлкО ï¿®13%
  4. 🀩🀩ашлО пПсЌПтреть ОМфП ï¿®53%
  5. 🀩 . . . . ï¿®11%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

custom 519770038431491645110custom 53797445789055947348custom 52447524124675495947custom 53935327596605861977

Signed Ù  Н𝑎𝑛𝑎𝑘𝑜 Û°. ݁ [𝑠he/ℎer]𔓕‌֎ #𝑁eu𝑣illettes𝑊ifeïžµ #𝑁euvi𝑙𝑙ette𝑘𝑖sser @

4 Oct 2025, 06:02 UTC≈1,120 views34 reactionsread 15 August 2026
Photo

🀩🀩🀩🀩🀩🀩🍭🍭 🀩🀩🀩🍭🍭 𝆭 𝆌 ✹ 🀩🀩 ۪𓋜] 𝒊𝑖𝑛𝑛𝑖𝔢𝓁𝒟𝑠𝑡 🍭 🍭🍭🍭🍭🍭🍭🍭🍭 🍭 𓈒 𓆇࣪ » 𝔐𝑜𝓇𝑒 : 🍭 🀩 {𝐷𝑁𝐌} : [Бᥲဋᥲ]. РᥱᥔЎᥱρы, Мёʙᥙρᥙဋ᧘ᥙ, 𐋏ёʙᥙ᧘᧘ᥱ᎛ ᥊ ԿжуМ 𐌡ᥙ, ᥲᎊρᥱ᥎᥎ᥙʙМыᥱ ᧘юЎᥙ𝆹 🍭🍭🍭🍭🍭🍭🍭🍭 🀩 {𝒯𝒜𝑖𝑛 𝒟𝑐𝑒} : 𐌏᥎᎛ᥲ᧘ьМыᥱ ᥰᥱᥔρᥙМᎊᥙ ᥎ 𐋏ёʙᥙ᧘᧘ᥱ᎛᧐ⲙ, 𐌺уМᥙκᥙЎᥲ ᥊ Дᥲဋᥲᥔ.𝆹 🍭🍬🍬🍬🍭🍬🍬🍬🍭 Öº 𝇂𝇄֎ 🍭🍭 ➌࣪ ࣧ ࣮ 🍭 ♯ 🀍𝑒𝑢𝑣𝑖𝓁𝓁𝑒𝑡𝑡𝑒'𝑠 🀍𝑜𝓋𝑒 ✹✹

custom 524475241246754959410custom 539353275966058619710custom 51977003843149164517custom 53797445789055947347

Signed Ù  Н𝑎𝑛𝑎𝑘𝑜 Û°. ݁ [𝑠he/ℎer]𔓕‌֎ #𝑁eu𝑣illettes𝑊ifeïžµ #𝑁euvi𝑙𝑙ette𝑘𝑖sser @

4 Oct 2025, 06:02 UTC≈1,050 views41 reactionsread 15 August 2026
Photo

🀩🀩🀩 ֎˖✚𝆩🀩🀩🀩 🀩🀩࣪ ÖŽ 𝅄 🍭🍭🍭🍭🍭🍭 🀩 🍭🍭 [ 𝔏𝑜𝓋𝑒 𓈒 Û«ÖŽ ͝ 𓆇࣪ 🀩 𝆌 𝆭 𝔏𝒟𝓈𝓉𝆹 ] 🍭 🀩 🍭📃🍭 🀩🀩 🍭🍭 🀩🌟 𝒩𝑒𝓊𝓋𝒟𝓁𝓁𝑒𝓉𝓉𝑒 [𝓂𝓎 𝒷𝑒𝓁𝑜𝓋𝑒𝒹 𝒜𝓊𝓈𝒷𝒶𝓃𝒹] 𓂃 🌟ИсОва [𝓂𝓎 𝒷𝑒𝓈𝓉 𝒻𝓇𝒟𝑒𝓃𝒹] НОкПль  КарОк  КОПвлО  𝑂лОвье  Сухарь  Ева  ЭлечаМ ЧерешМя  РэМ  ДжПля  КвОкс  НяЌ НяЌ  МелПк  Кела  КОлька  Вёр  ЛПЎя  Салл  ВОллаМель  КвОрр  ЭйверО  🍭🍭🍭🍭🍭🍭🍭 🍭🍭🍭🍭 🀩🀩 🀩

custom 539353275966058619714custom 524475241246754959412custom 51977003843149164519custom 53797445789055947346

Signed Ù  Н𝑎𝑛𝑎𝑘𝑜 Û°. ݁ [𝑠he/ℎer]𔓕‌֎ #𝑁eu𝑣illettes𝑊ifeïžµ #𝑁euvi𝑙𝑙ette𝑘𝑖sser @

4 Oct 2025, 06:01 UTC≈1,030 views28 reactionsread 15 August 2026
Photo

🀩🀩 🍭🍭🍭🍭🍭🍭 📌 🀩𝆩🀩ℑ𝓃𝒻𝑜࣪ ÖŽ 𝆌 ࣭ ࣮ 𓄰 ֮˖ 🀩 ֎˖✚✚○ 🍭🀩🍭 🀩 🍭🍭 🍭 𝆹𝐻𝑎𝑛𝑎𝑘𝑜 (𝑜𝑛𝑙𝑊)࣪ ÖŽ 𝅄 🍭🍭 ✹[ ֎˖𝑆𝒜𝑒𝆩/𝒜𝑒𝑟➌]✹ 𓈒 Û«ÖŽ ۪𓋜 🀩🀩🀩🀩 🀩 ✚𝐵𝒟𝑟𝑡𝒜𝑑𝑎𝓏 🍭 🀩🀩 ➌࣪ ֮˖ 🪜 🔠🔠𝆹🔠🔠 🀩 🍭🍭🍭🍭🍭🍭🍭 🀩 🍭🀩🀩🍭 🀩 ♯𝒩𝑒𝓊𝓋𝒟𝓁𝓁𝑒𝓉𝓉𝑒'𝓈 𝒲𝒟𝒻𝑒 Û° . ݁ 𝆭 𝇂𝇄֎ ♯𝒩𝑒𝓊𝓋𝒟𝓁𝓁𝑒𝓉𝓉𝑒𝒊𝒟𝓈𝓈𝑒𝓇 𓄰 🀩🀩🀩 🍭🍭🍭🍭🍭🍭🍭 🀩𝆹𝔉𝑎𝑛𝑔𝑜𝑚𝑠 : 🀩🀩🀩 💫🅱🅱 

🕊8custom 52447524124675495947custom 53935327596605861975custom 51977003843149164514custom 53797445789055947344

Signed Ù  Н𝑎𝑛𝑎𝑘𝑜 Û°. ݁ [𝑠he/ℎer]𔓕‌֎ #𝑁eu𝑣illettes𝑊ifeïžµ #𝑁euvi𝑙𝑙ette𝑘𝑖sser @

3 Apr 2025, 13:16 UTC≈1,190 views28 reactionsread 15 August 2026
Forwarded from @repost_ifPhoto

❀ :: репПстМОте эту запОсь, еслО ваш любОЌый персПМаж — МёвОллет ! 〣 @repost_if

☃10🐳10❀‍🔥4🍓4

Signed ⊱ ٠ 𝐻𝑎𝑛𝑎𝑘𝑜 ࣪⊰ [she/her]! #neuvilletteswife #jupiterkisser

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

4 Oct 2025, 06:02 UTCAnonymous Poll152 voters

✚✚𝆹 𝆭 🀩🀩🀩🍭

  1. 🀩 🀩руг ï¿®11%
  2. 🀩 🀩МакПЌый ï¿®13%
  3. 🀩 🀩з ПЎМПгП флуЎа/рПлкО ï¿®13%
  4. 🀩🀩ашлО пПсЌПтреть ОМфП ï¿®53%
  5. 🀩 . . . . ï¿®11%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 12 most recent posts we hold, published 28 January 2025 to 17 May 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

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

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.

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

“۰ 𓄰. ࣧ ࣮𝓗𝑎𝑛𝑎𝑘𝑜'𝓌 𝓘𝑛 ࣮𝑓𝑜𝆹𝅥.˙𝆹[📋𝆩🌊]𓂅” (@neuvillettessoulmate), 9 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/neuvillettessoulmate.

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.