Telegram RegisterThe public register of Telegram
Telegram profile photo for °•𝑫𝒐𝒖𝒃𝒍𝒆 𝑳𝒊𝒇𝒆 ᵗʳᵃⁿˢˡᵃᵗᶦᵒⁿˢ°•

Channel

°•𝑫𝒐𝒖𝒃𝒍𝒆 𝑳𝒊𝒇𝒆 ᵗʳᵃⁿˢˡᵃᵗᶦᵒⁿˢ°•

@DoubleLifetranslations

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

4subscribers

+0 since we began measuring on 25 September 2026

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

Register entry

Telegram ID-1004425668110
TypeChannel
Username@DoubleLifetranslations
First recorded25 September 2026
Last confirmed live25 September 2026
Measurements held2
On Telegramt.me/DoubleLifetranslations

Growth

425 Sept 2026, 08:47 — 4 subscribers25 Sept 2026, 09:22 — 4 subscribers25 Sept 2026, 08:4725 Sept 2026, 09:22
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 3–5 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Sept 2026, 09:224no change
25 Sept 2026, 08:474first reading

Engagement

11 posts held, back to 16 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 · 30 days
672.5%
avg views ÷ 4 subscribers
Avg views / post
26.9
10 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
11
of 11 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 23 September 2026
Posts held11 (16 September 2026 – 23 September 2026)
Views total269
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken25 Sept 2026, 09: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.

What this channel posts

Photos
6
Links
3

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

Recent posts

23 Sept 2026, 17:26 UTC4 viewsread 25 September 2026
Forwarded from @YOHIOloidailyPhoto

🤍🤍🤍😬 W E L C O M E🤍 T O 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 🤍🦷🦷🦷🦷🦷🦷🦷🦷🦷l o i d 🤩🤩 d a i l y+c f ☺️ 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 🤩YOHIOloid (ヨヒオロイド) — вокалоид, разработанный компанией PowerFX Systems AB в сотрудничестве с VocaTone. Выпущен в сентябре 2013 года для движка VOCALOID 3. 🤩Озвучен шведским певцом и автором песен YOHIO, который предоставил английский и японский голосовой банк. 🤩Внешность основана на образе самого артиста. 🤩О характере YOH…

23 Sept 2026, 17:25 UTC3 viewsread 25 September 2026
Forwarded from @Teto_NabereshnayaPhoto

░▒• ℘𝐓 ℘ᨵ꯱tׁׁׅׅ ⫸📢 ╹╷╹٭╹〣╷🕸╷╹╻╻🐾╹〣╭┆ ¿⚊♣⚊ ⌕ ⚋ ╭𓃚🆈️️️️🅾🆄 🅻🅸🅺🅴🪽𝙏ᥱТ᥆?彡📢┆ ⌗ ▀▀ ༅☥ ┆ ≪﹏ 🕳️ сюда что-то написать ━ ◑ ━━━━━ ▣ ━━━━━ ◐ ♣🍷 ░▒ ࿏ 〰︎〰︎ ࿏ ⌗༅ • ⦅🆇᥆чᥡ kᥲнᥲл ᥴ в᥆kᥲᥴинтᥲми! 🔳⦆ 🎵💬 ဣ ⁂ • ищᥱшᑲ д⍴ᥡжᥱлюбн᥆ᥱ мᥱᥴтᥱчк᥆ в в᥆кᥲфд?🪽 🪗 ࿏ • или в᥆᥆бщᥱм любишᑲ в᥆kᥲᥴинт᥆…

20 Sept 2026, 07:18 UTC16 viewsread 25 September 2026
Photo

°•𝑨𝒅𝒎𝒊𝒏𝒊𝒔𝒕𝒓𝒂𝒕𝒊𝒐𝒏°• 🔪Содᴀ {онᴀ/ᴇё} – ʙᴧᴀдᴇᴧᴇц 🕊️Янᴀ {он/онᴀ/оно} – ʙᴧᴀдᴇᴧᴇц 🪼Гᴧиᴄᴛ {онᴀ/ᴇё} – ᴄоʙᴧᴀдᴇᴧᴇц

18 Sept 2026, 20:54 UTC20 viewsread 25 September 2026
Photo

ⲏⲁⲃυⲅⲁⳡυя° •ρτ πоςτ •ϐπ πоςτ ────── ୨୧ ────── •Ωραϐιλα καςτιηгоϐ •Ακτιϐηьᵻε καςτιηгι

18 Sept 2026, 20:46 UTC19 viewsread 25 September 2026
Photo

°•ᥲⲕⲧυⲃⲏыᥱ ⲕᥲᥴⲧυⲏ𐔏υ°• – ~ 𝒟𝑜𝓊𝒷𝓁𝑒 𝓁𝒾𝒻𝑒 𝓉𝓇𝒶𝓃𝓈𝓁𝒶𝓉𝒾𝑜𝓃𝓈 ꨄ︎

16 Sept 2026, 20:19 UTC17 viewsread 25 September 2026
Video

°•ηƿɑɞυʌɑ κɑς੮υⲏɾ૦ɞ°• На большинство персонажей кастинги будут выкладываться сразу на голос и вокал. Озвучить нужно и то, и другое, но если вы совсем не умеете петь, то при загрузке своей работы уточняйте это и что вы подаётесь только на голос. Также из-за этого на голос и вокал одного персонажа мы можем выбрать двух разных людей, так что не обижайтесь Оформлять свои работы нужно обязательно так, иначе заявка не бу…

16 Sept 2026, 19:57 UTC16 viewsread 25 September 2026
Video

。・𝓜𝓟 𝓹𝓸𝓼𝓽 。・ 0+ Не принимаем каналы с темой расчленёнки, селфхарма, 18+, гомофобии/трансфобии Списки больше 6 каналов – отказ Пост удаляем спустя 2 дня °•ⲣⲧⲱⲁⲧь эⲧⲟ

16 Sept 2026, 19:32 UTC165 viewsread 25 September 2026
Photo

𝘿𝙤𝙪𝙗𝙡𝙚 𝙇𝙞𝙛𝙚 𝙩𝙧𝙖𝙣𝙨𝙡𝙖𝙩𝙞𝙤𝙣𝙨 – Любишь секай и мечтаешь услышать русскую озвучку? – Хочешь петь или озвучивать персонажа, но тебя не берут? 𝗖𝗼𝗻𝗴𝗿𝗮𝘁𝘂𝗹𝗮𝘁𝗶𝗼𝗻𝘀! 𝗬𝗼𝘂'𝗿𝗲 𝗶𝗻 𝘁𝗵𝗲 𝗿𝗶𝗴𝗵𝘁 𝗽𝗹𝗮𝗰𝗲! {Мы будем озвучивать песни, ивенты и много чего ещё! ^^ Оставайся с нами и всё увидишь . . #ртпост #projectsekai #студияозвучки ~ 𝒟𝑜𝓊𝒷𝓁𝑒 𝓁𝒾𝒻𝑒 𝓉𝓇𝒶𝓃𝓈𝓁𝒶𝓉𝒾𝑜𝓃𝓈 ꨄ︎

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

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.

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

“°•𝑫𝒐𝒖𝒃𝒍𝒆 𝑳𝒊𝒇𝒆 ᵗʳᵃⁿˢˡᵃᵗᶦᵒⁿˢ°•” (@DoubleLifetranslations), 4 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/DoubleLifetranslations.

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.