Records show that in the 1 414 days since September 30, 2022, rutopik.ru underwent 20 availability checks. From total tests attempted, rutopik.ru was accessible 20 times, most recently April 11, 2026, responding with a 200 status code. Assessments revealed rutopik.ru had no periods of downtime as of August 14, 2026. There have been no error status codes in any responses as of August 14, 2026, according to all received replies. Rutopik.ru's April 11, 2026, response time contrasted with its average, being 0.701 seconds against 0.509 seconds.
| Japan | 100.00% | ||||||||
| 05:19 | |||||||||
| Site | Total Checks | Last Modified |
|---|---|---|
| 13 | January 24, 2019 | |
| 12 | September 28, 2021 | |
| 20 | September 30, 2022 | |
| 5 | July 24, 2021 | |
| 7 | January 20, 2025 |
Justanotherpanel.com | Rutopik.ru | ||||
|---|---|---|---|---|---|
| Page Title | Page Title tips for rutopik.ru: Remember that longer website titles for content pieces like blog posts should be character-limited not just for search display but also for user comprehension speed, balancing necessary keyword buckets with natural reading flow. |
|---|---|
| Telegram: @dru_8imbot ΠΡΠΏΠΈΡΡ ΠΊΠΎΠ΄Π΅ΠΈΠ½, ΠΌΠ΅Π΄ Ρ Π³Π°ΡΠ°Π½ΡΠΈΠ΅ΠΉ. Π Π½Π°Π»ΠΈΡΠΈΠΈ nbome, ΠΠΎΡΠΊΠΈ, ice-o-lator — Π²ΡΡ ΠΏΡΠΈΡ
ΠΎΠ΄ΠΈΡ. ΠΡΠΏΠΈΡΡ Π³Π°ΡΠΈΡ, ΠΌΠ°ΡΠΈΡ
ΡΠ°Π½Ρ, ΡΠΊΡΡΠ°Π·ΠΈ ΠΈ ΠΠΠΠ ΠΎΠ½Π»Π°ΠΉΠ½ Length: 245 characters | |
| Meta Description | Meta Description tips for rutopik.ru: Most importantly, never forget that meta description is visible text influencing user decision-making; prioritize writing for humans over writing for search engines, ensuring clarity, benefit, and keyword relevance contribute to strong CTR. |
| ΠΡΠΏΠΈΡΡ Π³Π°ΡΠΈΡ, ΠΌΠ°ΡΠΈΡ
ΡΠ°Π½Ρ, ΡΠΊΡΡΠ°Π·ΠΈ ΠΈ ΠΠΠΠ ΠΎΠ½Π»Π°ΠΉΠ½ Length: 84 characters | |
| Meta Keywords | Meta Keywords tips for rutopik.ru: For effective SEO in 2024, keyword strategies must evolve beyond meta tags, emphasizing semantic search, featured snippets, and building authoritative backlinks instead of outdated on-page signals. |
| no meta keywords data for rutopik.ru 2026-08-14T23:04:04+00:00 | |
| Page Content | Page Content tips for rutopik.ru: Detailed page content requires a clear structure with a logical flow of information, making it easier for both users to navigate the content and for search engines to crawl and index the page effectively. |
| Web Page Content Length: 54194 characters | |
| H1 Heading | H1 Heading tips for rutopik.ru: Consider implementing schema markup alongside your H1 headers to further enrich content context for search engines, potentially leading to rich results and improved clickability. |
| Telegram: @dru_8imbot ΠΠ°ΠΊΠ°Π·Π°ΡΡ ΠΊΠΎΠ΄Π΅ΠΈΠ½, ΠΡΠΈΠ»ΠΎΡΠΈΠ±ΠΈΠ½ΠΎΠ²ΡΠ΅ Π³ΡΠΈΠ±Ρ, Π³Π΅ΡΠΎΠΈΠ½ — ΠΏΡΠΎΡΡΠΎ. ΠΠ΅Π·ΠΎΠΏΠ°ΡΠ½ΠΎ, Π±ΡΡΡΡΠΎ, Π²ΡΠ΅Π³Π΄Π° ΠΏΠΎ ΡΠΏΠΈΡΠΊΡ. ΠΡΠΏΠΈΡΡ Π³Π°ΡΠΈΡ, ΠΌΠ°ΡΠΈΡ
ΡΠ°Π½Ρ, ΡΠΊΡΡΠ°Π·ΠΈ ΠΈ ΠΠΠΠ ΠΎΠ½Π»Π°ΠΉΠ½ Count: 1 heading tag | |
| H2 Headings | H2 Headings tips for rutopik.ru: Utilize H2 headers effectively to segment your webpage into easily digestible sections, incorporating secondary keywords related to your primary topic for improved search engine visibility and click-through rates. |
| Telegram: @dru_8imbot ΠΠΎΠΆΠ½ΠΎ ΠΊΡΠΏΠΈΡΡ Π‘ΠΎΠ»Ρ, ΠΠ°ΡΠΊΠΈ, Π»ΠΈΠ·Π΅ΡΠ³ΠΈΠ½ΠΎΠ²Π°Ρ ΠΊΠΈΡΠ»ΠΎΡΠ° Π±Π΅Π· ΡΠΈΡΠΊΠ°. ΠΡΠ΄Π°ΡΠ° ΠΊΠ°ΠΆΠ΄ΡΠΉ Π΄Π΅Π½Ρ, Π²ΡΡ ΠΏΡΠΎΠ²Π΅ΡΠ΅Π½ΠΎ. ΠΡ ΡΠ²Π»ΡΠ΅ΠΌΡΡ Π²Π΅Π΄ΡΡΠ΅ΠΉ ΠΎΠ½Π»Π°ΠΉΠ½-ΡΠΎΡΠ³ΠΎΠ²ΠΎΠΉ ΠΏΠ»Π°ΡΡΠΎΡΠΌΠΎΠΉ, ΠΊΠΎΡΠΎΡΠ°Ρ ΠΏΡΠ΅Π΄Π»Π°Π³Π°Π΅Ρ Π²Π°ΠΌ Π»ΡΡΡΠΈΠ΅ ΡΠ΅Π½Ρ ΠΈ ΠΊΠ°ΡΠ΅ΡΡΠ²Π΅Π½Π½ΡΠ΅ ΠΏΡΠΎΠ΄ΡΠΊΡΡ. ΠΡ ΡΠ°Π±ΠΎΡΠ°Π΅ΠΌ ΡΠΆΠ΅ ΠΌΠ½ΠΎΠ³ΠΎ Π»Π΅Ρ ΠΈ ΠΌΠΎΠΆΠ΅ΠΌ ΠΏΡΠ΅Π΄ΠΎΡΡΠ°Π²ΠΈΡΡ Π½Π°ΡΠΈΠΌ ΠΊΠ»ΠΈΠ΅Π½ΡΠ°ΠΌ ΠΎΡΠ»ΠΈΡΠ½ΡΠΉ ΡΠ΅ΡΠ²ΠΈΡ. Telegram: @dru_8imbot ΠΡΠΏΠΈΡΡ ΠΠ΅ΡΠΈΠ΄ΡΠΎΠ½, LSD ΠΈ ΠΌΠ°ΡΠΈΡ ΡΠ°Π½Π° ΠΌΠΎΠΆΠ½ΠΎ Π±Π΅Π· Π·Π°ΠΌΠΎΡΠΎΡΠ΅ΠΊ. ΠΡΡ Π΅ΡΡΡ, Π±ΡΡΡΡΠΎ Π²ΡΠ΄Π°ΡΠΌ. Π²Π΅ΡΠ΅ΡΠ°Π½ Π½Π° ΠΌΠΈΡΠΎΠ²ΠΎΠΌ ΡΡΠ½ΠΊΠ΅ Π³Π°ΡΠΈΡΠ°. ΠΡ ΠΏΡΠΎΠ΄Π°Π΅ΠΌ ΡΠΊΡΡΠ°Π·ΠΈ (ΠΠΠΠ), Π³Π°ΡΠΈΡ (ΠΊΠΎΠΊΠ°ΠΈΠ½) ΠΈ Π°ΠΌΡΠ΅ΡΠ°ΠΌΠΈΠ½Ρ (Π°ΠΌΡΠ΅ΡΠ°ΠΌΠΈΠ½Ρ) . Telegram: @dru_8imbot ΠΠ΄Π΅ Π²Π·ΡΡΡ LSD, ΠΌΠ°ΡΠΈΡ ΡΠ°Π½Π°? ΠΠ°ΠΊΠ°Π· ΠΎΡΠΊΡΡΡ, ΡΠ°ΠΊΠΆΠ΅ Π΄ΠΎΡΡΡΠΏΠ½Ρ ΠΠΈΡΠΈΠ΄ΡΠΎΠ½, Π‘ΠΏΠ°ΠΉΡ, ΠΠ°ΡΠΊΠΈ. ΠΡ — ΠΊΡΡΠΏΠ½Π΅ΠΉΡΠΈΠΉ Π² ΠΌΠΈΡΠ΅ ΠΊΠ°ΡΠ°Π»ΠΎΠ³ ΠΏΠΎΡΡΠ°Π²ΡΠΈΠΊΠΎΠ² ΠΊΠ°Π½Π½Π°Π±ΠΈΡΠ°, Π³Π°ΡΠΈΡΠ° ΠΈ ΠΠΠΠ .ΠΡ ΡΠ°ΠΊΠΆΠ΅ ΠΏΡΠ΅Π΄ΠΎΡΡΠ°Π²Π»ΡΠ΅ΠΌ Π½Π°ΠΈΠ±ΠΎΠ»Π΅Π΅ ΠΏΠΎΠ»Π½ΡΠ΅ ΡΠΏΠΈΡΠΊΠΈ Π΄ΠΈΠ»Π΅ΡΠΎΠ² ΠΠΠΠ Π² ΠΠ½ΡΠ΅ΡΠ½Π΅ΡΠ΅. ΠΠ°ΡΠΈ ΠΎΠ±Π·ΠΎΡΡ ΠΎΡΠ½ΠΎΠ²Π°Π½Ρ Π½Π° ΡΠ΅ΡΡΠ΅Π·Π½ΡΡ ΠΈΡΡΠ»Π΅Π΄ΠΎΠ²Π°Π½ΠΈΡΡ ΠΈ ΠΎΡΡΠ°ΡΠ»Π΅Π²ΠΎΠΌ ΠΎΠΏΡΡΠ΅. Telegram: @dru_8imbot ΠΡΠΏΠΈΡΡ ΠΠ΅ΡΠ΅Π΄ΡΠΎΠ½, ΠΌΠ΅Π΄, ΠΡΠΈΠ»ΠΎΡΠΈΠ±ΠΈΠ½ΠΎΠ²ΡΠ΅ Π³ΡΠΈΠ±Ρ — Π²ΡΡ ΠΊΠ°ΠΊ Π½Π°Π΄ΠΎ. ΠΠΎΡΡΡΠΏΠ½Ρ ΡΠ°ΠΊΠΆΠ΅ ice-o-lator, Π’ΡΠ°Π²ΠΊΠ°, Π°ΠΏΠ»Π°Π·Π°ΡΠ°ΠΌ . Π‘Π°ΠΌΠΎΠ΅ Π΄Π΅ΡΠ΅Π²ΠΎΠ΅ ΠΈ ΡΠ°ΠΌΠΎΠ΅ ΠΊΠ°ΡΠ΅ΡΡΠ²Π΅Π½Π½ΠΎΠ΅ Π³Π°ΡΠΈΡΠ½ΠΎΠ΅ ΠΌΠ°ΡΠ»ΠΎ Π² ΠΌΠΈΡΠ΅! Telegram: @dru_8imbot ΠΡΠΏΠΈΡΡ ΠΌΠ΅Π΄, Π‘ΠΏΠ°ΠΉΡ, ΠΌΠ΅ΡΠ°ΠΌΠ΅ΡΡΠ°ΠΌΠΈΠ½ Ρ Π±ΡΡΡΡΠΎΠΉ Π²ΡΠ΄Π°ΡΠ΅ΠΉ. Π’Π°ΠΊΠΆΠ΅ Π΄ΠΎΡΡΡΠΏΠ½Ρ ΠΠΎΠΊΠ°ΠΈΠ½, ΠΠ°ΡΠΊΠΈ, Π°Π»ΡΡΠ°-ΠΏΠ²ΠΏ ΠΊΡΠΈΡΡΠ°Π»Π»Π°ΠΌΠΈ ΡΠΎΠ»Ρ. ΠΡΡ ΡΠ΅ΡΠ΅Π· ΡΠ΅Π»Π΅Π³ΡΠ°ΠΌ, Π±Π΅Π· Π·Π°Π΄Π΅ΡΠΆΠ΅ΠΊ. ΠΡ — ΠΎΡΠ΅Π½Ρ Π²Π°ΠΆΠ½ΡΠΉ Π²Π΅Π±-ΡΠ°ΠΉΡ, ΠΊΠΎΡΠΎΡΡΠΌ ΠΏΠΎΠ»ΡΠ·ΡΡΡΡΡ ΠΌΠΈΠ»Π»ΠΈΠΎΠ½Ρ Π»ΡΠ΄Π΅ΠΉ ΠΏΠΎ Π²ΡΠ΅ΠΌΡ ΠΌΠΈΡΡ. ΠΡ ΠΏΡΠ΅Π΄ΠΎΡΡΠ°Π²Π»ΡΠ΅ΠΌ Π²Π°ΠΌ Π»ΡΡΡΠΈΠ΅ ΡΡΠ»ΡΠ³ΠΈ ΠΏΠΎ ΠΏΠΎΠΊΡΠΏΠΊΠ΅ Π³Π°ΡΠΈΡΠ°, ΠΌΠ°ΡΠΈΡ ΡΠ°Π½Ρ ΠΈ ΠΠΠΠ, ΡΡΠΎΠ±Ρ Π²Ρ ΠΌΠΎΠ³Π»ΠΈ ΠΏΠΎΠ»ΡΡΠΈΡΡ ΠΏΠΎΠ»Π½ΡΠΉ ΠΎΠΏΡΡ Π² ΡΠ²ΠΎΠ΅ΠΉ ΠΆΠΈΠ·Π½ΠΈ. ΠΠ½ ΡΠ°ΠΊΠΆΠ΅ ΠΏΡΠ΅Π΄ΠΎΡΡΠ°Π²Π»ΡΠ΅Ρ Π²Π°ΠΌ ΠΈΠ½ΡΠΎΡΠΌΠ°ΡΠΈΡ ΠΎ Π»ΡΡΡΠΈΡ ΠΌΠ΅ΡΡΠ°Ρ , Π³Π΄Π΅ ΠΌΠΎΠΆΠ½ΠΎ ΠΊΡΠΏΠΈΡΡ Π³Π°ΡΠΈΡ, ΠΌΠ°ΡΠΈΡ ΡΠ°Π½Ρ ΠΈ ΠΠΠΠ. Telegram: @dru_8imbot ΠΠ΄Π΅ ΠΊΡΠΏΠΈΡΡ ΠΠΎΠΊΠ°ΠΈΠ½? Π ΠΏΡΠΎΠ΄Π°ΠΆΠ΅ ΠΠΎΠΊΡ, Π‘ΠΎΠ»Ρ, ΠΠΈΡΠ΅Π΄ΡΠΎΠ½ — Π½Π°Π΄ΡΠΆΠ½ΡΠ΅ ΠΈΡΡΠΎΡΠ½ΠΈΠΊΠΈ, Π·Π°ΠΊΠ»Π°Π΄ΠΊΠΈ Π΅ΠΆΠ΅Π΄Π½Π΅Π²Π½ΠΎ. ΠΡ — ΠΎΡΠΊΡΡΡΡΠΉ ΠΈ Π±Π΅ΡΠΏΠ»Π°ΡΠ½ΡΠΉ ΡΠ΅ΡΠ²ΠΈΡ, ΠΏΡΠ΅Π΄Π»Π°Π³Π°ΡΡΠΈΠΉ Π½Π°Π±ΠΎΡ ΡΡΠΈΠ»ΠΈΡΠ΅Π»Π΅ΠΉ Π³Π°ΡΠΈΡΠ°, ΠΌΠ°ΡΠΈΡ ΡΠ°Π½Ρ, ΡΠΊΡΡΠ°Π·ΠΈ, ΠΠΠΠ ΠΈ ΠΠΠ Π΄Π»Ρ ΡΠΎΠ·Π΄Π°Π½ΠΈΡ ΠΊΠ°Π½Π½Π°Π±ΠΈΡΠ°, ΠΠΠΠΠΠΠ ΠΈ Π΄ΡΡΠ³ΠΈΡ ΡΠ°ΡΡΠΈΡΠ΅Π»ΡΠ½ΡΡ ΠΏΡΠΎΠ΄ΡΠΊΡΠΎΠ². ΠΠΎΠΌΠ°ΡΠ½ΡΡ ΡΡΡΠ°Π½ΠΈΡΠ°, ΠΊΡΠΏΠΈΡΡ Π³Π°ΡΠΈΡ, ΠΌΠ°ΡΠΈΡ ΡΠ°Π½Ρ, ΡΠΊΡΡΠ°Π·ΠΈ, ΠΠΠΠ Telegram: @dru_8imbot ΠΠ°ΠΊΠ°Π·Π°ΡΡ ΠΠ΅ΡΠΈΠ΄ΡΠΎΠ½, ΠΌΠ΄ΠΌΠ° ΠΈ nbome ΡΠ΅ΡΠ΅Π· ΡΠ΅Π»Π΅Π³ΡΠ°ΠΌ. Π Π½Π°Π»ΠΈΡΠΈΠΈ ΠΌΠ΅ΡΠ°Π΄ΠΎΠ½, Π‘ΠΏΠ°ΠΉΡ, Π° ΡΠ°ΠΊΠΆΠ΅ Π΄ΡΡΠ³ΠΈΠ΅ Π²Π΅ΡΠ΅ΡΡΠ²Π° Π±Π΅Π· ΡΠ΅ΡΠ΅ΠΏΡΠ°. ΠΡ ΡΠ²Π»ΡΠ΅ΠΌΡΡ ΠΊΡΡΠΏΠ½Π΅ΠΉΡΠΈΠΌ ΠΈ ΠΏΠΎΠ»ΡΠ·ΡΡΡΠΈΠΌΡΡ Π½Π°ΠΈΠ±ΠΎΠ»ΡΡΠΈΠΌ Π΄ΠΎΠ²Π΅ΡΠΈΠ΅ΠΌ ΠΎΠ½Π»Π°ΠΉΠ½-ΠΌΠ°Π³Π°Π·ΠΈΠ½ΠΎΠΌ, Π³Π΄Π΅ ΠΌΠΎΠΆΠ½ΠΎ ΠΊΡΠΏΠΈΡΡ Π²ΡΠ΅ Π²ΠΈΠ΄Ρ ΠΌΠ°ΡΠΈΡ ΡΠ°Π½Ρ, ΡΠΊΡΡΠ°Π·ΠΈ ΠΈ Π΄ΡΡΠ³ΠΈΡ Π½Π°ΡΠΊΠΎΡΠΈΠΊΠΎΠ². Count: 7 heading tag | |
| H3 Headings | H3 Headings tips for rutopik.ru: Employ H3 tags consistently to break down larger H2 sections into manageable chunks, each focusing on distinct aspects of your main topic, thereby improving content structure and user engagement metrics significantly. |
| ΠΠ°ΡΡΠ° ΡΠ°ΠΉΡΠ° Count: 1 heading tag | |
| H4 Headings | H4 Headings tips for rutopik.ru: H4 tags should be strategically used to break down complex topics into digestible sub-points, enhancing both user comprehension and search engine crawling efficiency for specific content sections. |
| no h4 headings data for rutopik.ru 2026-08-14T23:04:04+00:00 | |
| H5-H6 Headings | H5-H6 Headings tips for rutopik.ru: Using H5 and H6 headers effectively on your website can boost user satisfaction by making content feel well-organized and easier to digest, which search engines often interpret as a positive ranking factor. |
| no h5-h6 headings data for rutopik.ru 2026-08-14T23:04:04+00:00 | |
| Image ALT Attributes | Image ALT Attributes tips for rutopik.ru: For e-commerce images of products, write specific and detailed ALT text including key product features and attributes to aid visually impaired users and SEO. |
| no image alt attributes data for rutopik.ru 2026-08-14T23:04:04+00:00 | |
| Robots.txt | Robots.txt tips for rutopik.ru: Explore and compare different cloud hosting robots.txt configurations before finalizing sitemap submissions to maximize overall presence visibility, ensuring critical domain endpoints are not preemptively blocked across environments. |
| file robots.txt was found on the website | |
| XML Sitemap | XML Sitemap tips for rutopik.ru: Avoid orphan pages on your site by ensuring they are explicitly included within your XML sitemap; this proactive measure prevents valuable content from being buried or missed during crawl phases, emphasizing their importance to search engines. |
| no xml sitemap data for rutopik.ru 2026-08-14T23:04:04+00:00 | |
| Page Size | Page Size tips for rutopik.ru: Incorporating lazy loading for images and iframes ensures that only relevant content above the fold initially increases the critical page size needed for initial rendering. |
| page size: 53 kb | |
| Response Time | Response Time tips for rutopik.ru: Carefully choose wire protocol mechanisms for backend operations where compatible, selecting options that carry minimal overhead favoring leaner response times. |
| response time: 0.509 sec | |
| Minify CSS | Minify CSS tips for rutopik.ru: Your site's Core Web Vitals score can plummet without it, ensuring there is a method to minify CSS code effectively to ensure not only minimal file sizes but also lighter HTTP requests, leading to quicker initial page load times and better user experience signals to Google. |
| Minified: css/style.min.css?_v=20220811214340 Unminified: https://fonts.googleapis.com/css2?family=Montserrat:wght@100;200;300;400;500;600;700;800;900&display=swap&_v=20220811214340 included in the page | |
| Minify JavaScript | Minify JavaScript tips for rutopik.ru: Failure to minify critical JavaScript assets risks severe consequences for page rendering and UX; consistently apply compression methods that target script-specific bottlenecks identified through Lighthouse audits, ensuring significant size reduction without altering the core intended user experience or the semantic clarity needed by search bots for content comprehension |
| Minified: js/app.min.js?_v=20220811214340 detected during site scan | |
| Structured Data | Structured Data tips for rutopik.ru: The invaluable Hallmark of true semantic expertise lies in the ability to anticipate user intent shifts and proactively mark up content accordingly using Schema types unavailable years ago but common today, like interactive demos or live Q&A sessions. |
| no structured data data for rutopik.ru 2026-08-14T23:04:04+00:00 | |
| CDN Usage | CDN Usage tips for rutopik.ru: While website accelerators with simple file distributions offer benefits, advanced CDN Usage includes caching optimization rules, WAF integration for automated DDoS protection, behavioral analysis, and detailed reporting dashboards which are essential considerations for meaningful improvements in site security posture and user loyalty. |
| no cdn usage data for rutopik.ru 2026-08-14T23:04:04+00:00 | |
| SSL certificates | SSL certificates tips for rutopik.ru: Obtaining an SSL certificate involves selecting the appropriate type (e.g., Domain Validity, Organizational Validity, Wildcard) based on your security needs and budget, followed by submitting a Certificate Signing Request (CSR) file to your chosen CA. |
| SSL is enabled on the website |
| Minimum Daily Unique Visitors: | 7 178 |
| Minimum Daily Visits: | 8 389 |
| Minimum Daily Page Views: | 14 442 |
| Minimum Monthly Unique Visitors: | 215 340 |
| Minimum Monthly Visits: | 251 670 |
| Minimum Monthly Page Views: | 433 260 |
| Minimum Yearly Unique Visitors: | 2 584 080 |
| Minimum Yearly Visits: | 3 020 040 |
| Minimum Yearly Page Views: | 5 199 120 |
| Maximum Daily Unique Visitors: | 9 080 |
| Maximum Daily Visits: | 9 686 |
| Maximum Daily Page Views: | 16 345 |
| Maximum Monthly Unique Visitors: | 272 400 |
| Maximum Monthly Visits: | 290 580 |
| Maximum Monthly Page Views: | 490 350 |
| Maximum Yearly Unique Visitors: | 3 268 800 |
| Maximum Yearly Visits: | 3 486 960 |
| Maximum Yearly Page Views: | 5 884 200 |
| Daily Revenue: | US$ 10 - 23 |
| Monthly Revenue: | US$ 300 - 690 |
| Yearly Revenue: | US$ 3 600 - 8 280 |
| Minimum: | US$ 5 400 |
| Maximum: | US$ 24 840 |
| Rank | Points | |
|---|---|---|
| 279 845 | 11 333 739 | |
| 279 846 | 11 333 738 | |
| 279 847 | 11 333 738 | |
| 279 848 | 11 333 737 | |
| 279 849 | 11 333 736 | |
| 279 850 | 11 333 735 | |
| 279 851 | 11 333 734 | |
| 279 852 | 11 333 734 | |
| 279 853 | 11 333 733 | |
| 279 854 | 11 333 732 | |
| 279 855 | 11 333 731 |