Channel
@reginalife1
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
634subscribers
-6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002519512936 |
|---|---|
| Type | Channel |
| Username | @reginalife1 |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/reginalife1 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 20:13 | 634 | -5 |
| 8 Aug 2026, 05:15 | 639 | -1 |
| 8 Aug 2026, 02:48 | 640 | no change |
| 7 Aug 2026, 18:35 | 640 | first reading |
7 posts held, back to 17 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 7 (17 July 2026 – 7 August 2026) |
| Views total | 2,311 |
| Reactions total | 747 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 02:48 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.
897 reactions across 7 posts, in 22 distinct kinds. The most used accounts for 10.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5203941530141752819 | 97 | 10.8% | |
| custom 5411544770168237920 | 79 | 8.81% | |
| custom 5440430594192349646 | 55 | 6.13% | |
| custom 5188402080766776741 | 48 | 5.35% | |
| custom 5278369280407145793 | 45 | 5.02% | |
| custom 5438468249404612096 | 45 | 5.02% | |
| custom 5280515312356203070 | 44 | 4.91% | |
| custom 5433855845370727300 | 44 | 4.91% | |
| custom 5287639859941372369 | 42 | 4.68% | |
| custom 5217449537295124789 | 41 | 4.57% | |
| custom 5258225192299150928 | 41 | 4.57% | |
| custom 5307820747329140508 | 40 | 4.46% | |
| custom 5215702902944859557 | 38 | 4.24% | |
| custom 6086767719917559031 | 38 | 4.24% | |
| custom 5258415120047948917 | 37 | 4.12% | |
| custom 5309977654135374142 | 34 | 3.79% | |
| custom 5309875305064712722 | 29 | 3.23% | |
| custom 5442788591367382815 | 24 | 2.68% | |
| custom 5215203299464087420 | 22 | 2.45% | |
| custom 5188638072039838932 | 21 | 2.34% | |
| 2 further kinds | 33 | 3.68% |
Custom emoji. Every row above is a 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 areTelegram’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 7 of the 7 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 897reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 17 July 2026 to 7 August 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.
~ сегодня с мамой ездили к тёте в сад, насобирали яблок 🍎🅿️ и каждый раз, когда бываю на даче, думаю: какой же это рай.можно приезжать на выходные,выращивать свои ягоды овощи и фрукты, отдыхать от городской суеты.просто мечта <3
custom 521520329946408742022custom 544043059419234964621custom 530987530506471272220custom 54384682494046120968
~ 🥞☕️//good morning сегодня решила побаловать себя домашними блинчиками. добавила к ним свежие ягоды, спелые фрукты и немного сгущёнки - получилось очень вкусно и красиво🍑🫧 делитесь в комментариях своими утренними тарелочками 💕
custom 543846824940461209637custom 530997765413537414234custom 544043059419234964634custom 53098753050647127229
🐢🩵🏖 { relax time }
custom 528763985994137236941custom 530782074732914050839custom 521570290294485955738custom 518863807203983893221
//+ 1 идеальный летний день 🍉✨ выбрались за город, зарядились природой, провели время с семьей и отпраздновали день рождения моей племянницы 💕 лето заканчивается быстрее, чем нам кажется. поэтому хочется успеть насладиться каждым теплым днем 🥹
custom 608676771991755903138custom 525841512004794891737custom 541154477016823792035custom 520394153014175281913custom 52876398599413723691
🍒 🕯{ evening time } ~ долго хотела черешню и вот наконец-то купила.наслаждаюсь любимой ягодой под турецкий сериал 🎞
custom 541154477016823792044custom 520394153014175281943custom 525822519229915092841custom 544712711822170064119custom 53078207473291405081
{ summer } 🪷🩰 //хочется, чтобы лето длилось чуть дольше. чтобы было больше прогулок до заката, зелёных аллей и вечеров, после которых остаётся приятная усталость💗 как прошли ваши выходные ?делитесь фотографиями <3
custom 527836928040714579345custom 520394153014175281941custom 521744953729512478941custom 544278859136738281524
тут был конкурс 🩵
custom 518840208076677674148custom 528051531235620307044custom 543385584537072730044custom 539793863160209136314
Showing the 7 most recent of 7 posts we hold for @reginalife1. 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 — 838,713 of 1,549,704entries 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.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“Regina life 🤍” (@reginalife1), 634 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/reginalife1.
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.