Telegram RegisterThe public register of Telegram
Telegram profile photo for Аренда жилья Лодзь

Channel

Аренда жилья Лодзь

@home_Lodz

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

8,236subscribers

+334 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001586492974
TypeChannel
Username@home_Lodz
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live4 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/home_Lodz

Growth

7,9028,2368,0697 August 2026 — 7,902 subscribers8 August 2026 — 7,911 subscribers10 August 2026 — 7,935 subscribers13 August 2026 — 7,996 subscribers16 August 2026 — 8,004 subscribers20 August 2026 — 8,030 subscribers24 August 2026 — 8,064 subscribers26 August 2026 — 8,106 subscribers29 August 2026 — 8,137 subscribers1 September 2026 — 8,191 subscribers4 September 2026 — 8,236 subscribers7 August 20264 September 2026
11 measurements spanning 28 days, net +334. 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 7,852–8,286 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 18:158,236+45
1 Sept 2026, 08:058,191+54
29 Aug 2026, 15:188,137+31
26 Aug 2026, 18:468,106+42
24 Aug 2026, 01:238,064+34
20 Aug 2026, 01:118,030+26
16 Aug 2026, 18:178,004+8
13 Aug 2026, 14:387,996+61
10 Aug 2026, 20:157,935+24
8 Aug 2026, 04:547,911+9
7 Aug 2026, 12:487,902first reading

Engagement

347 posts held, back to 7 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 19 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.26%
avg views ÷ 8,236 subscribers
Avg views / post
103
277 posts measured
Reaction rate
0.307%
reactions ÷ views · ER floor
Posts in window
277
of 347 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. It is computed over the 10 of 277 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 28 August 2026
Posts held347 (7 August 202628 August 2026)
Views total28,646
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 18: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.

Reaction mix

7 reactions across 7 posts, in 2 distinct kinds. The most used accounts for 85.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
685.7%
👍114.3%

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

Measured over the 347 most recent posts we hold, published 7 August 2026 to 28 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

28 Aug 2026, 18:25 UTC47 viewsread 28 August 2026
Photo

WYNAJMĘ KAWALERKĘ NA RETKINI 📍 Район: #Polesie 💰 Цена: 1300 zł [+580 zł медиа] 🔢 Комнаты: #1_комната 〽 Площадь: 34.0 м² 📜 Частное лицо 📆 28/08/2026 | 20:08

28 Aug 2026, 18:25 UTC44 viewsread 28 August 2026
Photo

DO WYNAJĘCIA NOWOCZESNA KAWALERKA W ŁODZI! 📍 Район: #Polesie 💰 Цена: 1600 zł [+500 zł медиа] 🔢 Комнаты: #1_комната 〽 Площадь: 27.0 м² 📜 Частное лицо 📆 28/08/2026 | 20:10

28 Aug 2026, 18:25 UTC38 viewsread 28 August 2026
Photo

MIESZKANIE 3 POKOJOWE 50M2 📍 Район: #Górna 💰 Цена: 2650 zł [+830 zł медиа] 🔢 Комнаты: #3_комнаты 〽 Площадь: 50.0 м² 📜 Частное лицо 📆 28/08/2026 | 20:13

28 Aug 2026, 17:59 UTC71 viewsread 28 August 2026
Photo

MIESZKANIE 2 POKOJOWE Z TARASEM W APARTAMENTOWCU 📍 Район: #Śródmieście 💰 Цена: 2690 zł [+510 zł медиа] 🔢 Комнаты: #2_комнаты 〽 Площадь: 47.0 м² 📜 Агентство 📆 28/08/2026 | 19:55

28 Aug 2026, 17:54 UTC75 viewsread 28 August 2026
Photo

WYNAJMĘ 2 POKOJE OD 1 WRZEŚNIA, UL. ŚMIGŁEGO RYDZA / UL. PRZYBYSZEWSKIEGO 📍 Район: #Górna 💰 Цена: 1900 zł [+900 zł медиа] 🔢 Комнаты: #2_комнаты 〽 Площадь: 46.0 м² 📜 Частное лицо 📆 28/08/2026 | 19:40

28 Aug 2026, 17:54 UTC70 viewsread 28 August 2026
Photo

2 POKOJOWE MIESZKANIE W APARTAMENTOWCU Z TARASEM 📍 Район: #Śródmieście 💰 Цена: 2400 zł [+440 zł медиа] 🔢 Комнаты: #2_комнаты 〽 Площадь: 30.0 м² 📜 Агентство 📆 28/08/2026 | 19:43

28 Aug 2026, 17:39 UTC90 viewsread 28 August 2026
Photo

MIESZKANIE NA WYNAJEM W ŁODZI GÓRNEJ PRZY UL. PŁOCKIEJ OD ZARAZ. 📍 Район: #Górna 💰 Цена: 1500 zł [+284 zł медиа] 🔢 Комнаты: #2_комнаты 〽 Площадь: 25.0 м² 📜 Частное лицо 📆 28/08/2026 | 19:30

28 Aug 2026, 17:34 UTC86 viewsread 28 August 2026
Photo

DWUPOKOJOWE MIESZKANIE W ŁODZI 📍 Район: #Polesie 💰 Цена: 2000 zł 🔢 Комнаты: #2_комнаты 〽 Площадь: 24.0 м² 📜 Частное лицо 📆 28/08/2026 | 19:23

28 Aug 2026, 17:29 UTC89 viewsread 28 August 2026
Photo

DO WYNAJĘCIA OD ZARAZ | NOWOCZESNE 2 POKOJE 34M2 + TARAS 34M2 + MIEJSCE GARAŻOWE | ŁÓDŹ BAŁUTY, UL.OKOPOWA | 6 PIĘTRO | OS. JARZĘBINOWE |BEZPOŚREDNIO 📍 Район: #Bałuty 💰 Цена: 2500 zł [+680 zł медиа] 🔢 Комнаты: #2_комнаты 〽 Площадь: 34.0 м² 📜 Частное лицо 📆 28/08/2026 | 19:11

28 Aug 2026, 17:24 UTC99 viewsread 28 August 2026
Photo

KAWALERKA NA WYNAJEM - CENTRUM /DWORZEC ŁÓDŹ FABRYCZNA/ UL. NAWROT 50 - OD 1 WRZEŚNIA 📍 Район: #Śródmieście 💰 Цена: 1850 zł 🔢 Комнаты: #1_комната 〽 Площадь: 27.0 м² 📜 Частное лицо 📆 28/08/2026 | 19:15

28 Aug 2026, 17:08 UTC116 views0 reactionsread 28 August 2026
Photo

KAWALERKA KAMIŃSKIEGO ŚRÓDMIEŚCIE RONDO SOLIDARNOŚCI 📍 Район: #Śródmieście 💰 Цена: 1400 zł [+700 zł медиа] 🔢 Комнаты: #1_комната 〽 Площадь: 31.0 м² 📜 Частное лицо 📆 28/08/2026 | 19:00

28 Aug 2026, 16:33 UTC129 viewsread 28 August 2026
Photo

WYNAJMĘ MIESZKANIE 📍 Район: #Polesie 💰 Цена: 2350 zł 🔢 Комнаты: #2_комнаты 〽 Площадь: 36.0 м² 📜 Частное лицо 📆 28/08/2026 | 18:22

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

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

“Аренда жилья Лодзь” (@home_Lodz), 8,236 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/home_Lodz.

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.