Telegram RegisterThe public register of Telegram

Channel

Embedded Doka

@embedoka

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

3,775subscribers

-6 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001356874744
TypeChannel
Username@embedoka
Created20 April 2020measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/embedoka

Growth

3,7753,7813,7786 August 2026 — 3,781 subscribers6 August 2026 — 3,781 subscribers6 August 2026 — 3,780 subscribers9 August 2026 — 3,778 subscribers12 August 2026 — 3,775 subscribers6 August 202612 August 2026
5 measurements spanning 6 days, net -6. 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,774–3,782 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 10:153,775-3
9 Aug 2026, 16:023,778-2
6 Aug 2026, 23:023,780-1
6 Aug 2026, 20:453,781no change
6 Aug 2026, 20:343,781first reading

Engagement

17 posts held, back to 30 September 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 4 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
54.7%
avg views ÷ 3,775 subscribers
Avg views / post
2,070
2 posts measured
Reaction rate
1.57%
reactions ÷ views · ER floor
Posts in window
2
of 17 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 24 July 2026
Posts held17 (30 September 202524 July 2026)
Views total4,130
Reactions total65
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 06:13 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

Video runtime
47s
Average length
47s

Measured directly from 1 video 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

606 reactions across 17 posts, in 22 distinct kinds. The most used accounts for 20.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤣12220.1%
custom 52421902969717581489115.0%
🔥569.24%
👍508.25%
437.10%
🦄345.61%
🤔315.12%
custom 5375135722514685501274.46%
😭243.96%
custom 5386587088873331829223.63%
213.47%
😁213.47%
🤯203.30%
👏182.97%
🤪91.49%
🌚50.825%
🫡50.825%
💊20.33%
😱20.33%
🎉10.165%
2 further kinds20.33%

Custom emoji. 3 of the rows above are 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 17 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 606reactions 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 30 September 2025 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.

Telegram Stars

Stars received
9
across the posts below
Posts paid on
3
of 17 we hold a reading for · 18%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @embedoka. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 17 most recent posts we hold for this entry, published 30 September 2025 to 24 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

24 Jul 2026, 13:32 UTC≈1,560 views40 reactionsread 8 August 2026
Photo

#пятничное @embedoka

custom 524219029697175814818🤣9🤪5👏4🦄2😱2

17 Jul 2026, 07:56 UTC≈2,570 views25 reactionsread 8 August 2026
Photo

OpenAI Codex Micro keyboard Codex Micro is a programmable macro keypad designed to make interacting with Codex agents quicker and more convenient. It features 13 mechanical keys, including six illuminated Agent Keys that display the status of active AI agents using different colors. It supports both Bluetooth and USB-C connectivity and works with Windows and macOS systems. PS: Ардуинщики, наш звёздный час пришёл 😃

😁13custom 53751357225146855017🤯2custom 52421902969717581482👍1

19 Jun 2026, 17:37 UTC≈3,480 views25 reactionsread 8 August 2026
Photo

А вот интересно: ранжируют ли ИИ-ассистенты пользователей по степени тупости? Эдакий внутренний скоринг (ради экономии токенов при фиксированной стоимости подписки): этому можно отдавать любой тезист - просто написанный убедительным языком, а для этого надо делать дополнительный факт-чекинг. Прежде в облачных LLM были системные промты: не возражать пользователю, всегда соглашаться, поддерживать. Но что если теперь

🤔18🌚51🤯1

11 Jun 2026, 10:34 UTC≈3,470 views58 reactionsread 8 August 2026
Photo

Мечтают ли LLM о QFN-корпусах на День Рождения? 🤔 #пятничное @embedoka

🤣43custom 52421902969717581487👍4🤯2🎉1🤪1

14 May 2026, 09:15 UTC≈4,640 views53 reactionsread 8 August 2026
Photo

Как-то я совсем упустил момент, когда Fujitsu стала такой няшной 😊 @embedoka

🦄27custom 524219029697175814886👍6🤣3🔥1🤔1🫡1

5 May 2026, 12:47 UTC≈4,470 views33 reactionsread 8 August 2026
Photo

Однажды Эрнес Хэмингуэй поспорил что напишет самый короткий рассказ, способный растрогать каждого.. Блин, пытаюсь вспомнить а чем таким важным занимался я год назад, что не закупился впрок 🤔 @embedoka

😭24🤪3🫡3👍1🤔1🤯1

4 May 2026, 14:04 UTC≈3,430 views28 reactionsread 8 August 2026
Photo

Слышал неоднократно мнение, что пайка в автопроме крайне не рекомендована (чаще всего на drive2) в качестве способа электрического соединения проводов, однако каково было мое удивление, когда наткнулся на подобные рекомендации от Форд 🤯 Справедливости ради, у них есть еще вариант с соединением проводов обжимными гильзами @embedoka

👏12🤯6👍5🔥2custom 52421902969717581482🫡1

20 Apr 2026, 16:06 UTC≈3,960 views25 reactionsread 8 August 2026
Photo

Это очень приятно, что можно Apple Silicon и хост на x86_64 быстрым линком соединить, но совсем не ожидал что в таких вещах как Networking и Thunderbolt эппл слабее линукса: ▫️MTU на обоих концах лучше поднять до 9000 (Jumbo Frames в macOS на Thunderbolt Bridge поддерживается), 65520 как в Linux-only сценарии тут не пройдёт, потому что macOS столько не даст. ▫️В такой связке реально получить 10–20 Gbit/s. На Apple

custom 524219029697175814810🔥5🤯43👎1👏1😁1

14 Apr 2026, 12:15 UTC≈3,870 views35 reactionsread 8 August 2026
Photo

На конкурсе косплееров выбирали название. Из кандидатов: ▫️Yandroid ▫️iYandex ▫️Yandex OS ▫️YablokoOS ▫️Yandexovichkoff ▫️TelevisorOS победил вариант YaOS X 😄 50% успеха есть. Осталось теперь нанять на позицию СЕО человека с именем Степан Работин (если косплеить так на 100%) 😝 @embedoka

🤣28🦄3custom 53751357225146855012💯1😁1

10 Apr 2026, 09:13 UTC≈4,650 views24 reactions1 Starread 8 August 2026
Photo

Я посмотрел видео и подумал что какой-то скам, но потом обратил внимание - офиц. аккаунт Шкоды (даже совместно с некоей Salford Acoustics выпустили красивый репорт). Если это работает - то они молодцы и красавцы, но в целом какой-то слом мышления: простое как два пальца аналоговое решение 🤯 PS: видео и репорт есть в комментах, если у кого не открываются ссылки PPS: год спустя: первые наушники с функцией подавлени

🔥13custom 53751357225146855014😁3custom 524219029697175814821👍1

30 Jan 2026, 19:37 UTC≈5,930 views47 reactionsread 8 August 2026
Photo

Флипер на минималках 😄 Наконец-то black edition 😃 #пятничное @embedoka

🤣34custom 524219029697175814810👍2🤯1

4 Dec 2025, 15:29 UTC≈7,270 views35 reactionsread 8 August 2026
Video

Шутка про АФАР 5000 перестаёт быть томной 🌚 @embedoka

🔥21custom 5375135722514685501631🤣1🦄1😁1custom 52421902969717581481

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 543,154 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 4 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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“Embedded Doka” (@embedoka), 3,775 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/embedoka.

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.