Job listings โ a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channelโs own recent posts on 10 August 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 why it has no browse page of its own yet.
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 word for word on 2 other registered channels. 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)
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. 3 of the 3 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 46 comparable posts for this entry, running 6 August 2026 to 7 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).
Across the whole group of 3, the earliest publisher we hold is @HUNTME_LOGISTICS. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_mutual ยท clone_source, last confirmed 7 August 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.
Also posting the same content
This channelโs posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable โ 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times โ 60%, no better than a coin flip โ because it depends on how deep our own crawl happened to reach into each channelโs history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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.
45 measurements spanning 76 days, net +2,519. 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 25,107โ28,382 and does not start at zero.
Measurement log โ every subscribers count we have recorded, most recent 20 of 45
Measured (UTC)
Subscribers
Change
22 Oct 2026, 16:31
28,004
+35
21 Oct 2026, 11:17
27,969
+28
20 Oct 2026, 07:16
27,941
+20
19 Oct 2026, 03:47
27,921
+36
18 Oct 2026, 01:40
27,885
+12
16 Oct 2026, 22:46
27,873
+13
16 Oct 2026, 01:06
27,860
+41
15 Oct 2026, 02:56
27,819
-4
14 Oct 2026, 01:41
27,823
+93
11 Oct 2026, 07:16
27,730
+32
7 Oct 2026, 01:41
27,698
+169
2 Oct 2026, 04:40
27,529
+598
18 Sept 2026, 16:40
26,931
+146
16 Sept 2026, 08:18
26,785
+86
14 Sept 2026, 15:57
26,699
+74
12 Sept 2026, 23:20
26,625
+65
11 Sept 2026, 02:15
26,560
+121
8 Sept 2026, 03:14
26,439
+91
4 Sept 2026, 20:59
26,348
+81
3 Sept 2026, 08:14
26,267
first reading
Engagement
1,531 posts held, back to 6 August 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 114 pages of Telegramโs post history, 20 posts per page.
ERR ยท 30 days
7.75%
avg views รท 28,004 subscribers
Avg views / post
2,170
724 posts measured
Reaction rate
0.145%
reactions รท views ยท ER floor
Posts in window
736
of 1,531 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 600 of 724 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days ยท latest post in window 23 October 2026
Posts held
1,531 (6 August 2026 โ 23 October 2026)
Views total
1,571,008
Reactions total
1,919
Forwards / comments
not exposed by the public surface โ not measured, not estimated
Readings taken
23 Oct 2026, 09:13 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
โ18,700
Videos
โ168
Links
โ2,070
Lifetime counters from Telegramโs own channel header, read 23 October 2026 โ not the date at the top of this page, which is when the subscriber count was last read. A count marked โ was rounded by Telegram before we ever saw it โ t.me prints these counters in full below 1,000 and to three significant figures above, so โ142,000 means somewhere between 141,500 and 142,499.
Video runtime
37s
Average length
37s
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
2,830 reactions across 720 posts, in 28 distinct kinds. The most used accounts for 37.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
โค
1,063
37.6%
๐
370
13.1%
๐ฅ
234
8.27%
๐ค
200
7.07%
customย 5400175888656531815
145
5.12%
โก
115
4.06%
๐
99
3.50%
๐ค
83
2.93%
๐ฏ
78
2.76%
โคโ๐ฅ
66
2.33%
๐
59
2.08%
๐
48
1.70%
๐
35
1.24%
๐ค
34
1.20%
โ
33
1.17%
๐พ
26
0.919%
๐ณ
26
0.919%
๐
24
0.848%
๐
21
0.742%
๐
20
0.707%
8 further kinds
51
1.80%
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id โ no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegramโs.
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 823 of the 1,000 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 2,830 reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 24 August 2026 to 23 October 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.
Telegram Stars
Stars received
6
across the posts below
Posts paid on
5
of 987 we hold a reading for ยท 0.5%
Most on one post
2
single highest reading
A paid reaction is a reader spending Telegram Stars โ bought with money โ on a post by @newvacancylogistics. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 24 August 2026 to 23 October 2026. Star counts above 1,000 reach us in Telegramโs short form and carry the same three-significant-figure rounding as everything else on this page.
๐Position: Fleet specialist
๐ผExperience: at least 6 months
๐Location: Tashkent,UZB
๐ตSalary: To be discussed in interview
๐Shifts: Flexible
Requirements:
Fluent English / Russian
Flexible fleet skills and experience work with repair shop, maintain truck for repair.
Able to work with Statistics
Finding Truck and Trailer Parts
Payments for services
Able to work with Penske
Ability to work with team
Quick decision makiโฆ
๐ข Company: Trucking Company
๐ผ Position: DAT/AMAZON DISPATCHER
๐จ๐ปโ๐ป Experience: at least 1 year +
๐ Location: Andijan. Uzbekistan
๐ต Salary: will be discussed๐ฅ๐ฐ
โฐ Shift: main
๐จ๐ปโ๐ป Available: 2 vacancies
โ NO REMOTE/ NO SERVICE
Requirements
โ age 20+
โ responsible man
โ self confidence
โ Fluent English
โ MUST know how to set up with brokers
โ๏ธโ๏ธโ๏ธONLY EXPERIENCED DISPATCHER
NO LEARNER, NO UPDATER, NO TRAINING
Applyโฆ
WE ARE HIRING ACCOUNTANTS!
๐ข Company: Trucking Company
๐ผ Position: Accounting
Number of vacancies: 2
๐จ๐ปโ๐ป Experience: With and without
๐ Location: Tashkent (Mirzo Ulugbek metro)
๐ต Salary: Discussed in interview
โฐ Shift: Main shift
๐จ๐ปโ๐ปNO REMOTE!
Required Skills :
- Strong English language skills
- Communication & Negotiation skills
- Problem solving skills
- Stress Resistant
Apply to @Avazbek_accounting with CV
Male Updater AMAZON | 4 months of experience
Able to speak Russian / English!!!
๐ข Company: Trucking company
๐ Region: Tashkent, Yakkasaray
๐ฐ Salary: Negotiable
Only males
โ Night shift / afterhours shift
NO REMOTE!!! Only professional candidates needed.
Please apply with your CV and do not bother without experienceโผ๏ธ
Contact: @Nozjon1994
โ Position: ELD Specialist
โ Experience: NOT REQUIRED
โ Region:Tashkent, Uzbekistan๐บ๐ฟ
โ Salary: Discussed during interview ๐ฐ
โ๏ธRequirements:
๐ Men aged 18-26(ONLY MALES)
๐ At least 3rd year university student! (Donโt apply if 1-2nd year student!!!)
๐ Proficiency in English and Russian;
๐ Shifts 15:00-23:00 and 23:00-07:00
๐ Being ready for interesting work process;
๐ We're ready to teach you everything from ZERO!
โฆ
WE ARE HIRING AMAZON DISPATCHER!!!!
๐ข Company: Trucking Company
๐ผ Position: PO DISPATCHER
๐จ๐ปโ๐ป Experience: at least 2 year
๐ Location: Tashkent
๐ต Salary: Percentage Bonuses ๐ฐ
โฐ Shift: Any shift
๐จ๐ปโ๐ปNO REMOTE
๐๐ปโโ๏ธ 23 years+
Requirements
โ Need mostly AMAZON based specialist!
โ Must know market
โ Ability to speak English fluently.
โ Must have experience to file a dispute to fix the performance.
โ Must have a profeโฆ
WE ARE HIRING DAT AND AMAZON DISPATCHER!!!!
๐ข Company: ATLANTIC UNION
๐ผ Position: Dispatcher
๐จ๐ปโ๐ป Experience: at least 2 years
๐ Location: Tashkent,UZB
๐ต Salary: will be discussed
โฐ Shift: Main shift
๐จ๐ปโ๐ปNO REMOTE!!!!!!!!
Age : (20 - 28 other age members do not disturb !!! )
Requirements:
โ Need Dispatchers
โ Only Males!!!
โ Ability to speak English fluently, Russian too!!!!
โ Good skills and experience booking loโฆ
๐ Position: ELD SPECIALIST
๐ Location: Yakkasaroy, Toshkent, Uzbekistan.
๐ Experience: At Least 1 year
๐ฃ Fluent English
๐ฐ Salary: Discussed on the interview
๐ Shift: Main ( 17:00 - 01:00 UZB TIME )
๐ข NO REMOTE
๐ค Gender: MALE
๐Age: At least 18 years old
๐ Responsibilities โผ๏ธ
โข Monitor and manage electronic logging device (ELD) records.
โข Ensure drivers comply with Hours of Service (HOS) regulations.
โข Review and cโฆ
APPLY WITH CV AND IELTS CERTIFICATE!!!
If you don't meet with requirements your messages will be ignored please don't waste your time!
Company name: RAYZA CORP LLC
Position: MALE DISPATCHERS (Cargo Van)
Experience: not required
Location: Tashkent, Uzbekistan (Yakkasaroy)
Salary: Will be discussed
IELTS at least 6.5
Age : 18-22 years old
Requirements:
-Fluent English is mandatory!
-Should be outgoing andโฆ
โ Position: ELD Specialist
โ Experience: NOT REQUIRED
โ Region:Tashkent, Uzbekistan๐บ๐ฟ
โ Salary: Discussed during interview ๐ฐ
โ๏ธRequirements:
๐ Men aged 18-26(ONLY MALES)
๐ At least 3rd year university student! (Donโt apply if 1-2nd year student!!!)
๐ Proficiency in English and Russian;
๐ Shifts 15:00-23:00 and 23:00-07:00
๐ Being ready for interesting work process;
๐ We're ready to teach you everything from ZERO!
โฆ
Updater Trailer Department Specialist
โ Sebzor, Toshkent
โ Salary : $800-$1000
โ Work Experience : 1 year
โ Age : 21 +
โ Onsite
Responsibilities:
- Trailer Management
- Providing trailers for Company dedicated lanes
- Ensuring all trucks and trailers are utilized efficiently and safely
- PTI checking
Required Skills :
- Strong English language skills
- Communication & Negotiation skills
- Problem solving skills
- Sโฆ
Position: AFTERHOURS UPDATE
Location: Mirobod, Tashkent, UZB
Salary: Will be discussed
Shift: Afterhours (02:00 am- 9:00 am
Experience: At least 6 months- 1 year
(DAT VAN loads)
Requirements:
- Males or Females!!!
- Fluent English
- STREET VAN LOADS
- Excellent communication skills
- If you do not meet these requirements, kindly refrain from applying.
- No trainees.
NO AMAZON!!!
Contact: @Jobs_CFT
โค5
Signed ๐๐๐๐๐๐๐๐๐
Showing the 12 most recent of 1,531 posts we hold for @newvacancylogistics. 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.
Posts edited after publishing
@newvacancylogistics edited 3 posts after it first published โ the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too โ this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
30 September 2026
Most recent edit
13 October 2026
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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
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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channelโs posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@newvacancylogistics named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handleโs history โ see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today โ not that anything โdiedโ. How this is measured.
Never seen alive
References a handle that is not a live channel โ we have no record it ever was one.
@call2action_sales named in 1 post, 13 August 2026 โ 13 August 2026
Channels Telegram recommends alongside this one
Telegramโs own answer, not this registerโs. When this register asks Telegramโs API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it โ never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegramโs; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Dispatch Hunter | Logistics Jobs @dispatchhunter ยท 28,130#1
Read from Telegramโs recommendation API, most recently 12 September 2026. Telegram holds a list like this for a small and growing share of the register โ how this is measured, and why most channel pages show nothing here.
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.
Dispatch Hunter | Logistics Jobs @dispatchhunter ยท 28,130 Telegram ranks this channel #1 of 45 here โ alongside 44 others โ read 10 September 2026
HUNTME | JOBS @huntmejob ยท 36,933 Telegram ranks this channel #1 of 42 here โ alongside 41 others โ read 2 September 2026
Toshkent Ish | ะ ะฐะฑะพัะฐ ะฒ ะขะฐัะบะตะฝัะต @clozjobs ยท 179,952 Telegram ranks this channel #15 of 49 here โ alongside 48 others โ read 2 September 2026
ะขัะฐะบัะธ ัะพะณ'ะฐะปะฐั๏ธยฎ๏ธ ๏ธ @truckchi_togalar ยท 43,773 Telegram ranks this channel #19 of 33 here โ alongside 32 others โ read 29 August 2026
F1 visa interview Experiences โ @f1interviewreviews ยท 75,594 Telegram ranks this channel #28 of 45 here โ alongside 44 others โ read 25 August 2026
Job Uzbekistan Airports @vacancyuzairports ยท 40,766 Telegram ranks this channel #32 of 70 here โ alongside 69 others โ read 30 August 2026
ISHBOR Toshkent @ishlar_kerak_bormi ยท 1,079,416 Telegram ranks this channel #45 of 73 here โ alongside 72 others โ read 8 August 2026
TURON WORLD XBA @turonworld ยท 54,946 Telegram ranks this channel #53 of 65 here โ alongside 64 others โ read 5 September 2026
Ishtopar.uz @ishtoparuz_kanal ยท 155,736 Telegram ranks this channel #56 of 65 here โ alongside 64 others โ read 12 August 2026
BBC Radio Podcast @bbc_radio_podcast ยท 36,243 Telegram ranks this channel #64 of 83 here โ alongside 82 others โ read 2 September 2026
ENGLISH PODCASTS ๐ง @Podcast_English_listening ยท 231,531 Telegram ranks this channel #65 of 79 here โ alongside 78 others โ read 11 August 2026
Ish Bor @ish_bor_toshkent_kerak_vakansiya ยท 854,272 Telegram ranks this channel #67 of 69 here โ alongside 68 others โ read 8 August 2026
hh.uz @headhunter_uz ยท 22,782 Telegram ranks this channel #72 of 76 here โ alongside 75 others โ read 20 September 2026
ManaVakansiya | Toshkentda Ish @manavakansiya_uz ยท 116,640 Telegram ranks this channel #72 of 79 here โ alongside 78 others โ read 14 August 2026
ISHTOP.UZ ๐ผ @ishtopuz_rasmiy ยท 288,213 Telegram ranks this channel #73 of 80 here โ alongside 79 others โ read 10 August 2026
TDIU Yoshlar ittifoqi @TDIU_YI ยท 20,254 Telegram ranks this channel #74 of 74 here โ alongside 73 others โ read 26 September 2026
Kasbdor.uz | Vakansiya @kasbdoruz ยท 29,045 Telegram ranks this channel #76 of 80 here โ alongside 79 others โ read 15 September 2026
TDIUโขTSUEโขะขะะญะฃ @tsueuzofficial ยท 31,027 Telegram ranks this channel #79 of 80 here โ alongside 79 others โ read 6 September 2026
Talimda ishlar | Talabalar uchun ish @talabalar_uchun_ish ยท 256 Telegram ranks this channel #81 of 83 here โ alongside 82 others โ read 11 September 2026
Beminnat vakant @beminnatvakant_ish ยท 50,346 Telegram ranks this channel #81 of 82 here โ alongside 81 others โ read 26 August 2026
This channel appears in 20 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 22 October 2026 โ this
entry's latest reading, not the date you are reading this.
โNew Vacancy Logistics ๐โ (@newvacancylogistics), 28,004 subscribers as measured 22 October 2026. Telegram Register, tgregister.com/channel/newvacancylogistics.
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.