Telegram RegisterThe public register of Telegram
Telegram profile photo for Turizm, otel, restoran vakansiyaları

Channel

Turizm, otel, restoran vakansiyaları

@turizmvakansiyalari

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

4,637subscribers

+98 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-1002105014836
TypeChannel
Username@turizmvakansiyalari
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 November 2026
Measurements held28
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/turizmvakansiyalari

Topic

Job listings — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 13 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 4 other registered channels. This entry also sits inside a group of 9 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@turizmvakansiyalari/1371 · this entry6 Aug 2026, 05:34 UTC@azvak1/189146 Aug 2026, 05:40 UTC1.006 minutes
@turizmvakansiyalari/1373 · this entry7 Aug 2026, 06:05 UTC@azvak1/189357 Aug 2026, 06:10 UTC1.005 minutes
@azvak1/189528 Aug 2026, 10:33 UTC@turizmvakansiyalari/1378 · this entry8 Aug 2026, 10:33 UTC1.00under a minute
@turizmvakansiyalari/1380 · this entry10 Aug 2026, 12:31 UTC@azvak1/1896910 Aug 2026, 12:48 UTC1.0017 minutes
@azvak1/1898511 Aug 2026, 08:27 UTC@turizmvakansiyalari/1382 · this entry11 Aug 2026, 08:28 UTC1.00under a minute
@turizmvakansiyalari/1383 · this entry11 Aug 2026, 11:34 UTC@azvak1/1899411 Aug 2026, 12:30 UTC1.0056 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@azvak111 (8/8 hand-verifiable sample passed)1.0017 minutesthis entry (9–2)
@azvakaz11 (8/8 hand-verifiable sample passed)1.0049 minutesthis entry (8–3)
@azvakaze7 (7/7 hand-verifiable sample passed)1.0022 minutesthis entry (6–1)
@qadinisleri6 (6/6 hand-verifiable sample passed)0.99under a minutethis entry (5–1)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 7 of the 7 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 32 comparable posts for this entry, running 30 July 2026 to 11 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 9 channels, the one whose matching posts we hold earliest is @surucuanbardar. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_mutual · clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 9 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

4,5374,6374,5877 August 2026 — 4,539 subscribers7 August 2026 — 4,537 subscribers10 August 2026 — 4,547 subscribers12 August 2026 — 4,549 subscribers16 August 2026 — 4,558 subscribers19 August 2026 — 4,579 subscribers22 August 2026 — 4,577 subscribers25 August 2026 — 4,587 subscribers28 August 2026 — 4,579 subscribers1 September 2026 — 4,590 subscribers4 September 2026 — 4,607 subscribers10 September 2026 — 4,616 subscribers14 September 2026 — 4,617 subscribers18 September 2026 — 4,619 subscribers26 September 2026 — 4,607 subscribers5 October 2026 — 4,605 subscribers11 October 2026 — 4,613 subscribers14 October 2026 — 4,602 subscribers17 October 2026 — 4,606 subscribers20 October 2026 — 4,612 subscribers23 October 2026 — 4,606 subscribers26 October 2026 — 4,602 subscribers29 October 2026 — 4,617 subscribers2 November 2026 — 4,614 subscribers5 November 2026 — 4,608 subscribers7 November 2026 — 4,607 subscribers11 November 2026 — 4,614 subscribers17 November 2026 — 4,637 subscribers7 August 202617 November 2026
28 measurements spanning 102 days, net +98. 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,522–4,652 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)SubscribersChange
17 Nov 2026, 03:454,637+23
11 Nov 2026, 17:554,614+7
7 Nov 2026, 23:564,607-1
5 Nov 2026, 02:554,608-6
2 Nov 2026, 03:074,614-3
29 Oct 2026, 16:284,617+15
26 Oct 2026, 17:174,602-4
23 Oct 2026, 11:504,606-6
20 Oct 2026, 17:044,612+6
17 Oct 2026, 14:384,606+4
14 Oct 2026, 15:094,602-11
11 Oct 2026, 14:154,613+8
5 Oct 2026, 06:004,605-2
26 Sept 2026, 23:224,607-12
18 Sept 2026, 01:364,619+2
14 Sept 2026, 00:194,617+1
10 Sept 2026, 01:594,616+9
4 Sept 2026, 11:404,607+17
1 Sept 2026, 02:374,590+11
28 Aug 2026, 15:374,579first reading

Engagement

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

Reaction mix

25 reactions across 15 posts, in 3 distinct kinds. The most used accounts for 56.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1456.0%
👎1040.0%
🌭14.00%

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

Measured over the 33 most recent posts we hold, published 30 July 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, 14:31 UTC180 viewsread 12 August 2026

Barmen, komi, ofisiant (qadın) tələb olunur Ətraflı tanış ol və müraciət et: https://azvak.az/vakansiyalar/barmen/14954 Barmen-kassir tələb olunur Ətraflı tanış ol və müraciət et: https://azvak.az/vakansiyalar/barmen/14955 Administrator, animator, Face art maker-nəzarətçi, xadimə tələb olunur Ətraflı tanış ol və müraciət et: https://azvak.az/vakansiyalar/administrator/14957 Barmen tələb olunur Ətraf…

11 Aug 2026, 14:22 UTC161 viewsread 12 August 2026

Xadimə-qabyuyan tələb olunur 🧹✨ LVOV Şokolad Evi vakansiya elan edir! 🍫 Vakansiya adı: Xadimə-qabyuyan ( maaş 530-580 Azn ) 💰 İş Şərtləri: 6 günlük iş həftəsi 📅 İş yeri: Cresent Mall, Ağ şəhər 🏢 ƏM rəsmi müqavilə 📄 Yaş həddi 30-55 👩‍🦱 Yemək pulu ilə təmin olunacaq 🍽 Bonus ilə təmin olunacaq 💸 Qeyd olunan tələblərə cavab verən namizədlər öz ərizə formalarını (CV) “Xadimə-qabyuyan” mövzusu altında [email protected] elektr…

11 Aug 2026, 11:52 UTC183 views1 reactionsread 12 August 2026

Commis (Kiçik Aşpaz) tələb olunur (Ağ Şəhər və Sea Breeze) İş yeri: (The Woo Restaurant: White City və Sea Breeze) Vəzifə öhdəlikləri: Təyin edilmiş stansiyada (soyuq və ya isti) məhsulların hazırlanmasın yerinə yetirmək. Sanitariya və təhlükəsizlik standartlarına uyğun işləmək İş günü sonunda stansiyanı səliqəli və təmiz vəziyyətdə təhvil vermək Reseptlərə və texniki kartlara tam uyğun məhsul hazırlamaq Yeni tex…

❤1

11 Aug 2026, 11:49 UTC168 views1 reactionsread 12 August 2026

Demi -Chef tələb olunur (Ağ Şəhər və Sea Breeze) İş yeri: (The Woo Restaurant: White City və Sea Breeze) Vəzifə öhdəlikləri: İsti və soyuq şöbə üzrə mətbəx əməliyyatlarının yüksək səviyyədə icrası; Modern Azərbaycan və Avropa mətbəxi üzrə biliklər; Mətbəxin bütün əməliyyatlarına nəzarət olunmasında iştirak etmək və komanda ilə koordinasiyalı fəaliyyət göstərmək; Texniki təhlükəsizlik, əməyin mühafizəsi qanunveric…

👎1

11 Aug 2026, 11:34 UTC188 views2 reactionsread 12 August 2026

Barmen tələb olunur (Ağ Şəhər və Sea Breeze) İş yeri: (The Woo Restautants : White City və Sea Breeze) Tələblər: Yaş həddi: 21–35 yaş; Dil bilikləri: Azərbaycan dili , Rus dili ( yaxşı səviyyədə ) və İngilis dili (arzuolunandır); Təcrübə: ən azı 1-2 il ; Vəzifə öhdəlikləri: Bar xidmətini təşkil etmək; Bar masası ətrafında müştərilərə alkoqol və digər içkilər üzrə xidmət göstərmək; Müştərilərə içki seçimində məlu…

👎2

11 Aug 2026, 08:28 UTC219 viewsread 12 August 2026

Pub-a ofisiant tələb olunur (qadın) Maaş: 600 AZN + bəxşiş + 3% Tələblər: Pub sahəsində iş təcrübəsi mütləqdir Rus dili vacibdir Müştərilərlə ünsiyyət bacarığı Səliqəli və məsuliyyətli olmaq İş şəraiti: Rəsmi iş Nahar verilir Stabil iş qrafiki Müraciət qaydası: Namizədlərdən CV-lərini [email protected] e-mail adresinə göndərə bilərlər. Vatsap:055 250 29 69

10 Aug 2026, 14:11 UTC303 viewsread 12 August 2026

Aşpaz tələb olunur Ətraflı tanış ol və müraciət et: https://azvak.az/vakansiyalar/aspaz/14896 Ofisiant (kişi) tələb olunur Ətraflı tanış ol və müraciət et: https://azvak.az/vakansiyalar/ofisiant/14862 Tur paketləri və xidmətlər üzrə satış təmsilçisi tələb olunur Ətraflı tanış ol və müraciət et: https://azvak.az/vakansiyalar/satis-mutexessisi-satis-temsilcisi/14863

10 Aug 2026, 12:31 UTC319 views2 reactionsread 12 August 2026

Keyfiyyətə nəzarət üzrə mütəxəssis tələb olunur Şirkət: Oba Market MMC Vəzifə: Market Şəbəkələrində Keyfiyyətə nəzarət üzrə mütəxəssis İş yeri: Cənub zonası İş qrafiki: 5 günlük iş rejmi; Vəzifə öhdəlikləri: Marketlərdə Qida Təhlükəsizliyi İdarəetmə Sisteminin tələblərinin tətbiqinə nəzarət etmək Qida təhlükəsizliyinin minimal tələbləri ilə bağlı personalın təlimləndirilməsini təmin etmək Marketlərdə plana …

❤2

8 Aug 2026, 10:39 UTC448 views1 reactionsread 12 August 2026

Hotelə kişi ofisiant tələb olunur İşə götürən: Teatro Boutique Hotel Tələblər: Namizəd: kişi Yaş həddi: 18-40 yaş arası, İş təcrübəsi vacibdir, təhsil orta, Dil bilikləri: ingilis dili (orta) Əməkhaqqı: 450 AZN+ tip İş saatı : 9 saat Əlavə imkanlar: nahar İş yerinin ünvanı: Əhməd Rəcəbli 1/19 Müraciət qaydası: [email protected] ; Vatsap: 0502750209

❤1

8 Aug 2026, 10:33 UTC438 viewsread 12 August 2026

Turizm şirkətinə müştəri xidməti üzrə əməkdaşlar tələb olunur (qadın-kişi) Şirkət: Baku City Tours *İş ərazi üzrə olacaq (iş ofis daxilində olmayacaq.).* Vəzifələr: * Tur paketləri və xidmətlər haqqında məlumat vermək * Müştəriləri cəlb etmək və yönləndirmək * Reklam və təqdimat işlərində iştirak etmək Tələblər: • Yaş həddi: 35-ə qədər * Ünsiyyət bacarığının yüksək olması * Aktiv və pozitiv olmaq * İngili…

7 Aug 2026, 14:11 UTC508 viewsread 12 August 2026

Tur Bələdçisi (Guide) tələb olunur Ətraflı tanış ol və müraciət et: https://azvak.az/vakansiyalar/beledci/14829 Ofisiant (Waiter) tələb olunur Ətraflı tanış ol və müraciət et: https://azvak.az/vakansiyalar/ofisiant/14858

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

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

AzVak.az - İş elanları / Vakansiyalar
@azvak1 · 31,891
Telegram ranks this channel #2 of 79 here — alongside 78 others — read 5 September 2026
AzVak - Azərbaycanda vakansiyalar: iş elanları / işlər / təcrübə proqramları / iş yeri
@azvakaz · 45,336
Telegram ranks this channel #8 of 93 here — alongside 92 others — read 27 August 2026
Hellojob.az - İş elanları/Vakansiyalar
@hellojobaz · 71,714
Telegram ranks this channel #34 of 85 here — alongside 84 others — read 26 August 2026
Edumap.az - Vakansiyalar, Təcrübə Proqramları və s.
@edumapazz · 26,273
Telegram ranks this channel #37 of 88 here — alongside 87 others — read 12 September 2026
SmartJob.az - iş elanları, vakansiyalar, təcrübə proqramları
@smartjobaz · 40,633
Telegram ranks this channel #50 of 80 here — alongside 79 others — read 29 August 2026
Glorri - Vakansiyalar 💼
@glori_jobs · 56,406
Telegram ranks this channel #50 of 89 here — alongside 88 others — read 26 August 2026

This channel appears in 6 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Turizm, otel, restoran vakansiyaları” (@turizmvakansiyalari), 4,637 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/turizmvakansiyalari.

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.