Telegram RegisterThe public register of Telegram

Channel

RINGO Project

@ringoproject

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

217subscribers

+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-1002035354391
TypeChannel
Username@ringoproject
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 9 August 2026
On Telegramt.me/ringoproject

Growth

2179 Aug 2026, 15:16 — 217 subscribers9 Aug 2026, 17:03 — 217 subscribers9 Aug 2026, 15:169 Aug 2026, 17:03
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 216–218 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 17:03217no change
9 Aug 2026, 15:16217first reading

Engagement

20 posts held, back to 27 August 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 20 posts for this entry, the most recent from 13 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
23m 53s
Average length
1m 24s

Measured directly from 17 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.

Reaction mix

807 reactions across 19 posts, in 21 distinct kinds. The most used accounts for 26.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💘21726.9%
19724.4%
❤‍🔥9912.3%
🔥759.29%
🥰566.94%
🍓536.57%
💋242.97%
🤯202.48%
🐳131.61%
👏101.24%
80.991%
🌭60.743%
🎉50.62%
🖕40.496%
😁40.496%
🤨40.496%
🍌30.372%
💅30.372%
🆒20.248%
👍20.248%
1 further kind20.248%

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 19 of the 20 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 807reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 27 August 2024 to 13 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

13 Jul 2026, 20:32 UTC200 views36 reactionsread 9 August 2026
Video

🍎Наша Мафую исполнила для вас песню Saisei! ――――――――――――――――― ✰ Вокал: Вум ✰ Монтаж: Кенчик ✰ Работа со звуком: Кенчик ✰ Перевод: Шимаи

💘186🔥6😁4🆒2

29 Apr 2026, 16:05 UTC933 views44 reactionsread 9 August 2026
Video

🍎 Поприветствуем актрису озвучки Шинономе Эны - Миориджи! (ремейк) ――――――――――――――――― ✰ Монтаж: Кенчик ✰ Работа со звуком: Кенчик ✰ Обложка: Дохи ✰ Перевод: Арчи

🤯17💘137🖕4🍓3

16 Sept 2025, 11:53 UTC≈1,370 views55 reactionsread 9 August 2026
Video

🍎 Поприветствуем актрису озвучки Тенмы Саки - Cули! ――――――――――――――――― ✰ Монтаж: Кенчик ✰ Работа со звуком: Кенчик ✰ Обложка: Дохи ✰ Перевод: MaoN

🍓2214🥰12💘4🔥3

10 Jul 2025, 09:02 UTC≈1,780 views53 reactionsread 9 August 2026
Video

🍎 Поприветствуем актрису озвучки Мизуки Акиямы - Аманэ! ――――――――――――――――― ✰ Монтаж: Кенчик ✰ Работа со звуком: Кенчик ✰ Сведение: Аманэ ✰ Обложка: Дохи ✰ Перевод: Аманэ

25💘12🔥8🤨4🥰4

7 Jul 2025, 10:03 UTC≈1,430 views32 reactionsread 9 August 2026
Video

🍎 Поприветствуем актрису озвучки Эму Отори - Чубу! ――――――――――――――――― ✰ Монтаж: Кенчик ✰ Работа со звуком: Кенчик ✰ Обложка: Дохи ✰ Перевод: Чубу

💘20❤‍🔥4💋4🍌3🥰1

3 Jul 2025, 16:52 UTC≈1,740 views32 reactionsread 9 August 2026
Video

🍎 Поприветствуем актёра озвучки Аояги Тойя - Арчи! ――――――――――――――――― ✰ Монтаж: Кенчик ✰ Работа со звуком: Кенчик ✰ Обложка: Дохи ✰ Перевод: Рей

💘18🔥63🤯3🍓2

27 Dec 2024, 14:59 UTC≈1,910 views46 reactionsread 9 August 2026
Video

🍎 Поприветствуем актрису озвучки Киритани Харуки - Teririn! ――――――――――――――――― ✰ Монтаж: Кенчик ✰ Работа со звуком: Кенчик ✰ Сведение: Teririn ✰ Обложка: Дохи ✰ Перевод: Лин

💘24🔥106🥰4💋2

13 Nov 2024, 14:40 UTC≈2,080 views57 reactionsread 9 August 2026
Video

🍎 Поприветствуем актрису озвучки Азусавы Кохане - Ай! ――――――――――――――――― ✰ Монтаж: Кенчик ✰ Работа со звуком: Кенчик ✰ Сведение: ЭльКормушка ✰ Обложка: Дохи ✰ Перевод: Гедо

31🔥12❤‍🔥11👍2💋1

6 Nov 2024, 15:08 UTC≈2,030 views66 reactionsread 9 August 2026
Video

🍎 Поприветствуем актрису озвучки Кусанаги Нене - Виви! ――――――――――――――――― ✰ Монтаж: Кенчик ✰ Работа со звуком: Кенчик ✰ Обложка: Дохи ✰ Перевод: Кирай

💘37❤‍🔥13🍓10🔥4🐳2

5 Nov 2024, 18:20 UTC≈1,700 views21 reactionsread 9 August 2026

🍎 К сожалению,роль Киритани Харуки свободна,и заявки на эту роль снова принимаются!🏷️ ----------------------------------- НЕАКТУАЛЬНО 🍏 Анкеты отправлять в @Ringopj_bot #Важно #уходактера

142❤‍🔥2💘2🔥1

31 Oct 2024, 11:03 UTC≈2,010 views38 reactionsread 9 August 2026
Video

🍎 Поприветствуем актрису озвучки Хошино Ичики - Скарлетт! ――――――――――――――――― ✰ Монтаж: Кенчик ✰ Работа со звуком: Кенчик ✰ Сведение: ЭльКормушка ✰ Обложка: Дохи ✰ Перевод: Мочимоника

21💘7❤‍🔥4🔥4🍓2

27 Oct 2024, 15:01 UTC≈2,110 views64 reactionsread 9 August 2026
Video

🍎 Поприветствуем актёра озвучки Камиширо Руи - Артос! ――――――――――――――――― ✰ Монтаж: Кенчик ✰ Работа со звуком: Кенчик ✰ Сведение: ЭльКормушка ✰ Обложка: Дохи ✰ Перевод: Гедо

40👏10🌭6🎉5🥰3

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

Citation-graph rank

Citation-graph rank — 983,895 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 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.

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

“RINGO Project” (@ringoproject), 217 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/ringoproject.

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.