Telegram RegisterThe public register of Telegram
Telegram profile photo for @dedrec

Channel

@dedrec

@dedrec

2 usernames

On this record: Growth · Engagement · Posts · Citations · Cite this entry

89subscribers

+5 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002050907565
TypeChannel
Usernames@aidenbio @dedrec
Created8 January 2024measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live22 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/dedrec

Growth

848986.57 August 2026 — 84 subscribers7 August 2026 — 85 subscribers9 August 2026 — 85 subscribers10 August 2026 — 86 subscribers15 August 2026 — 85 subscribers22 August 2026 — 89 subscribers7 August 202622 August 2026
6 measurements spanning 15 days, net +5. 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 83–90 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 14:2389+4
15 Aug 2026, 06:4685-1
10 Aug 2026, 15:4186+1
9 Aug 2026, 16:4685no change
7 Aug 2026, 22:3585+1
7 Aug 2026, 12:5084first reading

Engagement

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

Recent posts

30 Jan 2024, 19:00 UTC≈10,300 viewsread 15 August 2026
Photo

🕳️🕳️🕳️🕳🕳🕳🕳🕳🕳🕳🕳 🕳🕳🕳🕳🕳🕳🕳🕳🕳🕳🕳 Я 🔻 Aiden, Fullstack-разработчик с 7-ми летним коммерческим опытом. Мои проекты: 🔥🔥🔥 🔥🔥🔥📝📝📝📝📝 🔥🔥🔥⬇️ IT-агентство разработки под ключ Услуги: • Telegram MiniApps и боты • Мобильные приложения • Веб-сайты / Лендинги • Бэкенд-разработка • Поддержка проектов • Интеграция готовых решений • И другое… Обсудить проект — @v7manager @v7agency • v7-agency.com 1️⃣🔡1️⃣2️⃣1️⃣2️⃣3️⃣ 🧩🧩🧩 🧩🧩🧩📝📝

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

Mentions

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

“@dedrec” (@dedrec), 89 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/dedrec.

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.