Telegram RegisterThe public register of Telegram
Telegram profile photo for Работа в Испании 🇪🇸

Channel

Работа в Испании 🇪🇸

@work_spana

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

4,896subscribers

+68 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-1002071450621
TypeChannel
Username@work_spana
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live4 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/work_spana

Growth

4,8274,8964,861.56 August 2026 — 4,828 subscribers6 August 2026 — 4,828 subscribers6 August 2026 — 4,827 subscribers9 August 2026 — 4,849 subscribers12 August 2026 — 4,848 subscribers15 August 2026 — 4,849 subscribers18 August 2026 — 4,858 subscribers22 August 2026 — 4,873 subscribers25 August 2026 — 4,881 subscribers31 August 2026 — 4,887 subscribers4 September 2026 — 4,896 subscribers6 August 20264 September 2026
11 measurements spanning 29 days, net +68. 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 4,817–4,906 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 13:224,896+9
31 Aug 2026, 23:194,887+6
25 Aug 2026, 20:134,881+8
22 Aug 2026, 11:534,873+15
18 Aug 2026, 21:364,858+9
15 Aug 2026, 18:564,849+1
12 Aug 2026, 01:524,848-1
9 Aug 2026, 06:454,849+22
6 Aug 2026, 08:514,827-1
6 Aug 2026, 06:154,828no change
6 Aug 2026, 06:084,828first reading

Engagement

42 posts held, back to 2 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 9 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
16.6%
avg views ÷ 4,896 subscribers
Avg views / post
815
17 posts measured
Reaction rate
0.187%
reactions ÷ views · ER floor
Posts in window
17
of 42 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 1 of 17 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 11 August 2026
Posts held42 (2 August 202611 August 2026)
Views total13,854
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 06:20 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

21 reactions across 11 posts, in 2 distinct kinds. The most used accounts for 90.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1990.5%
👍29.52%

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

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

11 Aug 2026, 19:31 UTC401 viewsread 12 August 2026

Торревьеха Требуется няня для младенца. Обязательны рекомендации. ☎️ Контакты: @zouies #Torevieja@work_spana

11 Aug 2026, 15:05 UTC543 viewsread 12 August 2026

Торревьеха Требуется мастер по макетам и монтажник наружной рекламы. Что предстоит делать: • поклейка виниловой пленки; • изготовление и монтаж объемных букв; • производство и монтаж лайтбоксов; • работа с композитом; • изготовление и установка баннеров. ☎️ WhatsApp / Telegram / Телефон: +380678838181 Святослав #Torrevieja@work_spana

11 Aug 2026, 10:45 UTC600 viewsread 12 August 2026

Требуется мастер приёмщик в автосервис в Бенидорме. Обязательно знание испанского, английский - желательно, знание систем CRM и понимание технического устройства автомобилей. ☎️ WhatsApp: +34624696802 (высылайте резюме) #Benidorm@work_spana

10 Aug 2026, 13:57 UTC759 viewsread 12 August 2026

Торревьеха В связи с расширением набираем специалистов по уборке на постоянную работу в районах Avenida Habaneras и Punta Prima. 🚗 Очень важно иметь собственный автомобиль или другой личный транспорт, либо проживать рядом с указанными районами и иметь возможность самостоятельно добираться до объектов. ☎️ Пишите: @Joinmycat #Torrevieja@work_spana

10 Aug 2026, 12:17 UTC735 viewsread 12 August 2026

В автосервис в Торревьехе требуется маляр. ☎️ Пишите: @MaximVitov #Torrevieja@work_spana

10 Aug 2026, 10:31 UTC746 viewsread 12 August 2026

Бенидорм, Poniente Требуется няня для ребенка 4 лет на вечерние часы 5-6 дней в неделю. Игры по возрасту, развивающие занятия, чтение книг, стихи, песенки, изучение цветов и цифр, прогулки, активное общение и совместные игры. Опыт работы с детьми, профильное образование и рекомендации приветствуются. ☎️ Пишите: +34661406952 Натали #Benidorm@work_spana

10 Aug 2026, 07:25 UTC784 viewsread 12 August 2026

Для работы по провинции Аликанте требуется мастер широкого профиля на выполнение работ: Установка дверей, Установка техники (телевизоры с подключением, посудомоечные встроенные машины, варочные панели, духовые шкафы, холодильники), работа по гипроку, Сантехника, Установка кондиционеров, Сборка мебели и прочие работы. Обязательно опыт работы, свой автомобиль, базовый испанский язык. ☎️ Писать на WhatsApp: +346009449

9 Aug 2026, 19:54 UTC836 viewsread 12 August 2026

Требуется официант-бариста в кафе в Торревьехе. Обязательно знание английского и испанского. ☎️ WhatsApp: +34687772224 #Torrevieja@work_spana

9 Aug 2026, 11:30 UTC928 viewsread 12 August 2026

В ресторан в Бенидорме требуется мойщица посуды. ☎️ Пишите: @Oleksandr_Hamady #Benidorm@work_spana

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

Named by 12 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.

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

“Работа в Испании 🇪🇸” (@work_spana), 4,896 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/work_spana.

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.