Video, posted without a caption
Signed @. [𝗸𝗲𝗼𝗻ℌ𝗼] ໋* сперматозоид

Channel
@getup_oi
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
215subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003792118834 |
|---|---|
| Type | Channel |
| Username | @getup_oi |
| Description | 🩵: Get up - новая онлайн женская группа под прототипом Newjeans! ´ 𓈒 ৎ пытаемся передать вайб newjeans!🐰 наша старшая сестра: @asteriacvg наша младшая сестра: @Realme_gg бот: @GETUPoi_bot граф.оформа: @minaport_oi текст.оформа: @Kha0tyeona1 монтаж |
| Created | Between 1 February 2026 and 22 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/getup_oi |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 10:47 | 215 | no change |
| 7 Aug 2026, 18:26 | 215 | first reading |
17 posts held, back to 22 June 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 6 August 2026 |
|---|---|
| Posts held | 17 (22 June 2026 – 6 August 2026) |
| Views total | 350 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 10:47 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.
Lifetime counters from Telegram’s own channel header, read 8 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.
Measured directly from 2 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.
310 reactions across 8 posts, in 10 distinct kinds. The most used accounts for 13.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5352627568442898727 | 42 | 13.5% | |
| custom 5258477354124081646 | 41 | 13.2% | |
| custom 5210685702538299692 | 36 | 11.6% | |
| custom 5348087100816258356 | 35 | 11.3% | |
| custom 5348576435030226968 | 31 | 10.0% | |
| custom 6309583124221136359 | 31 | 10.0% | |
| custom 6147621174504329767 | 28 | 9.03% | |
| custom 5348222722998565755 | 25 | 8.06% | |
| custom 5256169689670777654 | 21 | 6.77% | |
| custom 5341481058862909480 | 20 | 6.45% |
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 8 of the 17 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 310reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 22 June 2026 to 6 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.
Video, posted without a caption
Signed @. [𝗸𝗲𝗼𝗻ℌ𝗼] ໋* сперматозоид
Sticker, posted without a caption
︎ ︎ ︎ 🎀💐` ☺️𝖮VER . {𝗽𝗎𝐫𝖾• 🥹 ^ 𝗚𝓔𝖳 𝗨𝖯 ¡ — 𝘤𝘂𝗍𝖾. #urmine - 🎁 ํ๐ *нᥱжн᧐. ︎🌸NJZ :: н𝖺𝐞𝗋𝗂𝐧.ຼ ໋° ํ ︎ — 🐈⬛) 𝗶 м𝗮𝗍𝘁𝖾𝗋 𝗍𝗼 у𝗈𝗎 ¿ 🎀🐰 🍄. @getup_oi :: * true '❤️ cover! ' song: MOMMAE (badji) 🩵 🎀🎁 @.[자기] ^໌? ໋* н𝗒𝘦𝐢𝗇 ່𝗆𝐢𝗇𝘫𝗂 🎀 🎀 ¿ 𝗶 ɾ𝖾𝗮𝗅𝗅𝗒 𝗅𝗶к𝖾 𝘆𝖺 — 🍭
custom 521068570253829969213custom 525847735412408164612custom 535262756844289872711custom 63095831242211363595custom 53485764350302269683custom 52561696896707776542custom 53482227229985657552custom 53480871008162583561
Sticker, posted without a caption
︎ ︎ ︎ 🎀💐` ☺️НТЕРAКТИВ. {𝗽𝗎𝐫𝖾•🥹 ^ 𝗚𝓔𝖳 𝗨𝖯 ¡ — 𝘤𝘂𝗍𝖾. #urmine - 🎁 ํ๐ *нᥱжн᧐. ︎🌸NJZ :: н𝖺𝐞𝗋𝗂𝐧.ຼ ໋ ํ ︎ — 🐈⬛) 𝗶 м𝗮𝗍𝘁𝖾𝗋 𝗍𝗼 у𝗈𝗎 ¿ 🎀🐰 🍄. g𝐞t up:: '❤️bingo! 'αω МУЗЫКА & @getup_oi ** 🎀🎁 @.[자기] ^໌? ໋* н𝗒𝘦𝐢𝗇 ່𝗆𝐢𝗇𝘫𝗂 🎀 ¿ 𝗶 ɾ𝖾𝗮𝗅𝗅𝗒 𝗅𝗶к𝖾 𝘆𝖺 — 🍭 🤩. любимые песни участников гет ап 🤩
custom 52561696896707776548custom 53480871008162583567custom 53482227229985657557custom 53414810588629094805custom 52584773541240816462custom 53485764350302269682custom 52106857025382996921custom 53526275684428987271
Sticker, posted without a caption
Signed •hanji•
︎ ︎ ︎ 🎀💐` ☺️𝖮VER . {𝗽𝗎𝐫𝖾• 🥹 ^ 𝗚𝓔𝖳 𝗨𝖯 ¡ — 𝘤𝘂𝗍𝖾. #urmine - 🎁 ํ๐ *нᥱжн᧐. ︎🌸NJZ :: н𝖺𝐞𝗋𝗂𝐧.ຼ ໋° ํ ︎ — 🐈⬛) 𝗶 м𝗮𝗍𝘁𝖾𝗋 𝗍𝗼 у𝗈𝗎 ¿ 🎀🐰 🍄. @getup_oi :: * true '❤️ cover! ' song: Umbrella ( sunhee ) 🩵 🎀🎁 @.[자기] ^໌? ໋* н𝗒𝘦𝐢𝗇 ່𝗆𝐢𝗇𝘫𝗂 🎀 🎀 ¿ 𝗶 ɾ𝖾𝗮𝗅𝗅𝗒 𝗅𝗶к𝖾 𝘆𝖺 — 🍭
custom 534822272299856575511custom 52584773541240816469custom 63095831242211363598custom 52561696896707776545custom 52106857025382996922custom 53480871008162583562custom 53485764350302269681
Sticker, posted without a caption
Signed •hanji•
︎ ︎ ︎ 🎀💐` ☺️𝖮VER . {𝗽𝗎𝐫𝖾• 🥹 ^ 𝗚𝓔𝖳 𝗨𝖯 ¡ — 𝘤𝘂𝗍𝖾. #urmine - 🎁 ํ๐ *нᥱжн᧐. ︎🌸NJZ :: н𝖺𝐞𝗋𝗂𝐧.ຼ ໋° ํ ︎ — 🐈⬛) 𝗶 м𝗮𝗍𝘁𝖾𝗋 𝗍𝗼 у𝗈𝗎 ¿ 🎀🐰 🍄. @getup_oi :: * true '❤️ cover! ' song: Either way ( sunny ) 🩵 🎀🎁 @.[자기] ^໌? ໋* н𝗒𝘦𝐢𝗇 ່𝗆𝐢𝗇𝘫𝗂 🎀 🎀 ¿ 𝗶 ɾ𝖾𝗮𝗅𝗅𝗒 𝗅𝗶к𝖾 𝘆𝖺 — 🍭
custom 521068570253829969215custom 534808710081625835614custom 630958312422113635913custom 53485764350302269685custom 53482227229985657554custom 52584773541240816463
Sticker, posted without a caption
︎ ︎ ︎ 🎀💐` ☺️R𝖮FILE . {𝗽𝗎𝐫𝖾• 🥹 ^ 𝗚𝓔𝖳 𝗨𝖯 ¡ — 𝘤𝘂𝗍𝖾. #urmine - 🎁 ํ๐ *нᥱжн᧐. ︎🌸NJZ :: н𝖺𝐞𝗋𝗂𝐧.ຼ ໋° ํ ︎ — 🐈⬛) 𝗶 м𝗮𝗍𝘁𝖾𝗋 𝗍𝗼 у𝗈𝗎 ¿ 🎀🐰 🩵. g𝐞t up:: * 😻'❤️ haerin ! 'αω name: sunny / age: 17 years old 🎀🎁 @.[자기] ? ໋* нa𝘦r𝐢𝗇 * get 🎀 ВРЕМ УЧАСТНИЦА 🎀 ¿ 𝗶 ɾ𝖾𝗮𝗅𝗅𝗒 𝗅𝗶к𝖾 𝘆𝖺 — 🤩
custom 535262756844289872716custom 534857643503022696813custom 614762117450432976713custom 52584773541240816465custom 52106857025382996923custom 53480871008162583563custom 52561696896707776542custom 63095831242211363592
18:ОО …
custom 53526275684428987278custom 53414810588629094804custom 53485764350302269683
Showing the 12 most recent of 17 posts we hold for @getup_oi. 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 — 691,255 of 1,169,250entries 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.
Named by 6 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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“᭝ ໋𝒢et uᴩ 𝖼𝗏. 𝗀𝗋𝗈𝗎𝗉” (@getup_oi), 215 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/getup_oi.
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.