Telegram RegisterThe public register of Telegram
Telegram profile photo for ᴄяᴏɯи

Channel

ᴄяᴏɯи

@xiaoshiphoto

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

19subscribers

+0 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-1003466217827
TypeChannel
Username@xiaoshiphoto
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live16 September 2026
Measurements held2
On Telegramt.me/xiaoshiphoto

Growth

199 August 2026 — 19 subscribers11 August 2026 — 19 subscribers9 August 202611 August 2026
2 measurements spanning 2 days. 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 18–20 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 17:4619no change
9 Aug 2026, 09:4619first reading

Engagement

10 posts held, back to 31 March 2026the 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 24 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
59
Links
7

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

42 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 61.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2661.9%
❤‍🔥716.7%
🔥49.52%
💋37.14%
💘12.38%
🥰12.38%

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 42 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 31 March 2026 to 24 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

24 Jul 2026, 16:25 UTC18 views5 reactionsread 11 August 2026
Forwarded from @cosplaykekePhoto

🤩🙂🙂🙂🙂🙂🙂🤩 🤩 🤩 🤩🤩🤩 - COS 🌟🌟🌟🌟🌟🌟🌟🌟 Раз уж Март 7 выбрала вас, я не стану ей мешать. Но прежде чем попрощаться, я хочу оставить кое-что на память~🌃 🖤 🖤PH

3💋1💘1

22 Jun 2026, 18:43 UTC58 views3 reactionsread 11 August 2026
Forwarded from @mirarhiaPhoto

☄️☄️ׄ . ˒˓ 🌟🌟🌟🌟 ׄ‌ ִׁ 🤩 ⌒ . ᶻ𝘇 🌟 🌟🌟🌟🌟 😕 😣 😗 𝑇ℎ𝑎𝑛𝑘 𝑦𝑜𝑢 𝑓𝑜𝑟 𝑏𝑒𝑖𝑛𝑔 𝑡ℎ𝑒 𝑣𝑖𝑐𝑡𝑖𝑚 𝑜𝑓 𝑚𝑦 𝑠ℎ𝑎𝑙𝑙𝑜𝑤 𝑒𝑚𝑜𝑡𝑖𝑜𝑛𝑠 . 😗🌟ִׄ 🌟🌟🌟🌟 😣 😣🎹𓈒 😕🌟 😘😗 ⟡ 𝑷𝒉𝒐𝒕𝒐𝒈𝒓𝒂𝒑𝒉𝒆𝒓

❤‍🔥21

22 Jun 2026, 18:43 UTC57 views2 reactionsread 11 August 2026
Forwarded from @m4rsallePhoto

❌🌹🌹🫶🫶🫶🫶🌹🌹 🎀🎀🎀🎀🎀🎀🎀🎀 ⭐⭐⭐⭐ 🌟𝓂ℴ𝒹ℯ𝓇𝓃 𝒶𝓊🌟 ⭐⭐⭐⭐ 𝘍𝘰𝘤𝘶𝘴𝘴𝘪𝘯𝘨 𝘦𝘹𝘤𝘭𝘶𝘴𝘪𝘷𝘦𝘭𝘺 𝘰𝘯 𝘵𝘩𝘦 𝘱𝘦𝘳𝘧𝘰𝘳𝘮𝘢𝘯𝘤𝘦 𝘢𝘯𝘥 𝘤𝘳𝘦𝘢𝘵𝘪𝘯𝘨 𝘵𝘩𝘦 𝘱𝘦𝘳𝘧𝘦𝘤𝘵 𝘴𝘤𝘦𝘯𝘦 - 𝘵𝘩𝘢𝘵'𝘴 𝘸𝘩𝘢𝘵 𝘦𝘷𝘦𝘳𝘺 𝘱𝘢𝘳𝘵𝘪𝘤𝘪𝘱𝘢𝘯𝘵 𝘴𝘩𝘰𝘶𝘭𝘥 𝘬𝘯𝘰𝘸 〰〰〰〰〰〰〰〰〰〰 💊𝘱𝘩𝘰𝘵𝘰𝘨𝘳𝘢𝘱𝘩𝘦𝘳 💊𝘮𝘰𝘥𝘦𝘭 #косплей #лука

1❤‍🔥1

16 May 2026, 17:16 UTC99 views9 reactionsread 11 August 2026
Photo

🅰️0️⃣🅰️🅰️🅰️🅰️🅰️🅰️➖ 🌺@m4rsalle 〰️〰️〰️〰️〰️〰️〰️〰️〰️

🔥43💋2

15 May 2026, 17:19 UTC78 views7 reactionsread 11 August 2026
Photo

🅰️0️⃣🅰️🅰️🅰️🅰️🅰️🅰️➖ *️⃣@LisenMi 〰️〰️〰️〰️〰️〰️〰️〰️〰️

❤‍🔥43

4 May 2026, 11:45 UTC86 views6 reactionsread 11 August 2026
Photo

🅰️0️⃣🅰️🅰️🅰️🅰️🅰️🅰️➖ *️⃣@LisenMi 〰️〰️〰️〰️〰️〰️〰️〰️〰️

6

3 May 2026, 10:58 UTC55 views3 reactionsread 11 August 2026
Forwarded from @LisenMiPhoto

🤩🤩〰〰〰〰〰〰〰〰 🤩🤩🥹𝓗𝔂𝓸𝓷𝓷𝓪 𝓭𝓮𝓴𝓲𝓰𝓸𝓽𝓸 𝓴𝓪𝓻𝓪 𝓨𝓪𝓽𝓽𝓮 𝓴𝓲𝓽𝓪 𝓴𝓸𝓷𝓸 𝓫𝓪𝓼𝓱𝓸 𝔀𝓪🥹🥹 𝓗𝓪𝓻𝓾𝓴𝓪 𝓽𝓸𝓸𝓴𝓾 𝓷𝓲 𝓪𝓽𝓽𝓪🥹🥹🥹 𝓚𝓲𝓻𝓪𝓫𝓲𝔂𝓪𝓴𝓪 𝓷𝓪 𝓫𝓾𝓽𝓪𝓲🥹🤩🤩 〰〰〰〰〰〰〰🤩🤩 [ PH ] [ COS ]

3

1 Apr 2026, 06:52 UTC85 views2 reactionsread 11 August 2026
Forwarded from @LisenMiPhoto

🌟🕧🕧🕧🕧🕧🕧🌟 🤩🤩🤩🤩🤩🤩🤩🤩 — …нᴇᴛ ᴛᴀᴋᴏᴦᴏ ядᴀ, ᴋᴏᴛᴏᴩый быᴧ бы ᴛᴀᴋиʍ жᴇ ужᴀᴄныʍ, ᴋᴀᴋ уᴧыбᴋᴀ жᴇнщины. Эᴛᴏ ᴨᴩᴀʙиᴧᴏ ᴄᴨᴩᴀʙᴇдᴧиʙᴏ ᴋᴀᴋ ʙ ɜᴀᴧᴀх ᴄᴀʍᴏᴦᴏ ᴩᴏᴄᴋᴏɯнᴏᴦᴏ дʙᴏᴩцᴀ, ᴛᴀᴋ и ʙ ᴦᴩяɜных ᴋᴏʍнᴀᴛᴀх ᴄᴀʍᴏᴦᴏ дᴇɯёʙᴏᴦᴏ дᴏʍᴀ удᴏʙᴏᴧьᴄᴛʙий.🌟 🤩🤩🤩🤩🤩🤩🤩🤩 [ 𝑷𝒉 ] [ 𝑪𝒐𝒔 ] 𝐑𝐭/𝐫𝐤💜🤩🤩🤩

2

31 Mar 2026, 19:07 UTC203 views3 reactionsread 11 August 2026
Photo

🅰️0️⃣🅰️🅰️🅰️🅰️🅰️🅰️➖ ❤️@cosplaykeke 〰️〰️〰️〰️〰️〰️〰️〰️〰️

3

31 Mar 2026, 19:06 UTC90 views2 reactionsread 11 August 2026
Photo

🅰️0️⃣🅰️🅰️🅰️🅰️🅰️🅰️➖ 🌿@cosplaykeke 〰️〰️〰️〰️〰️〰️〰️〰️〰️

1🥰1

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

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.

Named by

Channels on the register whose posts name this channel's handle.

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

“ᴄяᴏɯи” (@xiaoshiphoto), 19 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/xiaoshiphoto.

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.