Telegram RegisterThe public register of Telegram

Channel

ІТ спільнота ЛАМПА

@it_lampa

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

329subscribers

+0 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-1002844502537
TypeChannel
Username@it_lampa
DescriptionЛьвівська Асоціація Мітапів для Продуктивних Айтівців
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/it_lampa

Growth

3297 Aug 2026, 20:16 — 329 subscribers8 Aug 2026, 07:17 — 329 subscribers7 Aug 2026, 20:168 Aug 2026, 07:17
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 328–330 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 07:17329no change
7 Aug 2026, 20:16329first reading

Engagement

20 posts held, back to 8 April 2026the 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 · 30 days
125.7%
avg views ÷ 329 subscribers
Avg views / post
414
3 posts measured
Reaction rate
1.37%
reactions ÷ views · ER floor
Posts in window
3
of 20 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 7 August 2026
Posts held20 (8 April 20267 August 2026)
Views total1,241
Reactions total17
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 07:17 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
17
Videos
3
Links
44

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.

Video runtime
32s
Average length
32s

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

94 reactions across 18 posts, in 6 distinct kinds. The most used accounts for 67.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
6367.0%
🔥2021.3%
🤣55.32%
🥰33.19%
👏22.13%
👍11.06%

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 18 of the 20 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 94reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 8 April 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.

Recent posts

7 Aug 2026, 14:17 UTC138 views15 reactionsread 8 August 2026
Photo

Всіх з пʼятницею. Учора був на мітапі від SKELAR і радий був бачити активну частину нашого комʼюніті! В кулуарах за пивом народилась ідея — організувати імпровізований коворкінг. Маю на прикметі кілька закладів, де можна було б для початку просто зібратись на кілька годин, попрацювати поруч і поспілкуватись (або поспілкуватись поки працюватимуть агенти). Вважайте це бета-версією лампового коворкінгу. Якщо зайде — п

15

28 Jul 2026, 12:02 UTC499 views1 reactionsread 8 August 2026

Принагідно нагадуємо, що вже за кілька днів ми чекаємо вас на ламповому нетворкінг-івенті. Ніяких формальностей. → 30 липня, 17:00 → «ПРОСТІР», Парк Культури → Участь за донат від 300 грн у фонд KOLO Реєстрація на подію - https://luma.com/u4s1p69b

👍1

17 Jul 2026, 09:42 UTC604 views1 reactionsread 8 August 2026

Минулого разу ми зібрали повний зал, багато дискутували про ШІ, Разом з @RLabs_Builders посміялися, познайомилися з купою класних людей і закінчили все атмосферним нетворкінгом. Ваш фідбек після мітапу був настільки потужним, що ми вирішили не чекати осені й одразу зробити ще одну подію. Але цього разу - взагалі без формальностей. 🍹 Скіпаємо офіційну частину і починаємо одразу з афтепаті!! Що вас чекає: • 🎤 стенд

1

1 Jul 2026, 13:13 UTC422 views3 reactionsread 8 August 2026

Фото з останнього мітапу тиць тиць тиць

🔥3

27 Jun 2026, 07:59 UTC493 views8 reactionsread 8 August 2026
Photo

Придумайте підпис до фото 🤣 А ми поки підготуємо для вас решту)

🤣5👏21

22 Jun 2026, 12:09 UTC554 views2 reactionsread 8 August 2026

Це чергове нагадування про наш прийдешній мітап, який пройде 25го червня у Довгих Бурхливих Оплесках. Чекаємо всіх на 18-00 квитки

2

18 Jun 2026, 08:52 UTC532 views3 reactionsread 8 August 2026

Агов… Трохи є фото і відео з наших дебатів ТИЦЬ Дякуємо всім хто прийшов і допоміг створити атмосферу 💪 А тим часом нагадаємо про наш наступний івент 25.06 Опис і квитки тутка Так, реєстрація трохи багатослівна, але і набори джину від haister та WOOPʼи ми не щодня роздаємо 😏

🥰3

15 Jun 2026, 13:45 UTC433 views5 reactionsread 8 August 2026

25 червня ЛАМПА разом з нашими київськими друзями Ruby Labs проводимо мітап про те, як змінюється роль інженера в епоху AI. Два спікери: 🎙 Костянтин Гломозда — CTO & Co-Founder, Dym Solutions — про context engineering: як дати AI правильний контекст, щоб він перестав здогадуватись і почав реально допомагати вашій команді. 🎙 Сергій Бабіч — про те, чи забирає AI роботу програмістів, чи це просто чергова трансформаці

5

11 Jun 2026, 14:47 UTC324 views1 reactionsread 8 August 2026

Як знайти локацію! 14 поверх!!! Дзвіночок 🛎️ для входу!

1

10 Jun 2026, 13:36 UTC829 views1 reactionsread 8 August 2026
Photo

Спільното, добийте будь ласка два квитки - раптом хтось пропустив. Бо ж завтра ще анонсуємо наступний (менш кулуарний) мітап з розіграшем подарунків для учасників… Ви ж не хочете пропустити можливість бути early bird ще до офіційного анонсу? 😎️️️️️️ https://yoy.events/c/lampa/lampovi-debaty

1

8 Jun 2026, 11:01 UTC438 views3 reactionsread 8 August 2026
Photo

11 червня ЛАМПА робить дебати. Не панельку, не доповідь — саме дебати. Двоє людей, дві протилежні позиції. Тема: «Спеціалісти vs Дженералісти» За дженералістів топить Дмитро Брагінець — Engineering Manager в UINNO. Каже, що вузька спеціалізація — це пастка і ринок хоче адаптивних. Спеціалістів захищає Петро Карнаух — Software Engineer. Переконаний, що глибока експертиза б'є широку по всіх фронтах. Модерує Сергій

🔥21

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

Citation-graph rank — 225,504 of 1,345,403entries 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

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

“ІТ спільнота ЛАМПА” (@it_lampa), 329 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/it_lampa.

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.