Skip to main content
Rainbow Tours S.A. logo

Rainbow Tours S.A. — Investor Relations & Filings

Ticker · RBW ISIN · PLRNBWT00031 LEI · 25940062QUG3WEUEGE88 WAR Administrative and support service activities
Open in API
Filings indexed 1,024 across all filing types
Latest filing 2024-04-19 Legal Proceedings Report
Country PL Poland
Listing WAR RBW

About Rainbow Tours S.A.

https://r.pl/

Rainbow Tours S.A. is a tour operator and travel agency offering a comprehensive portfolio of travel services. The company specializes in organizing package holidays, guided tours, city breaks, and specialized vacations to a wide array of international destinations. Its product range includes all-inclusive stays, last-minute deals, and exotic long-haul trips. In addition to its consumer-facing business, the company operates an incoming tourism division that functions as a Destination Management Company (DMC), providing tailor-made group travel and business programs for foreign partners. Rainbow Tours also manages its own hotel brand and provides booking services for flights, accommodations, and car rentals.

Recent filings

Filing Released Lang Actions
1.6. Informacja Zarządu nt wyboru firmy audytorskiej JSF+SSF 2023
Legal Proceedings Report Classification · 95% confidence The document text provided is extremely long (1,882,835 characters) and appears to be the raw HTML/XML structure of a rendered document, including extensive CSS styling and font definitions. This structure suggests the content is a full, comprehensive report rather than a brief announcement. Given the length and the nature of the content being a full document structure, it is highly unlikely to be a short 'Report Publication Announcement' (RPA) or a simple 'Regulatory Filing' (RNS) which typically just announces the availability of a report. Since the content is too large and complex to definitively identify as a 10-K, IR, or AR based solely on the provided snippet (which is mostly boilerplate HTML), and it represents the full body of a filing, the most appropriate classification for a large, comprehensive, but unidentifiable regulatory document is the general fallback category, 'Regulatory Filings' (RNS), as it is a formal filing structure.
2024-04-19 Polish
Podpis
Regulatory Filings Classification · 95% confidence The provided document text consists almost entirely of XML structures, specifically related to digital signatures (xmlns:ds, SignatureValue, KeyInfo, X509Certificate, SignedProperties, etc.). This structure is characteristic of digitally signed regulatory filings or documents submitted electronically to regulatory bodies, often in formats like XML or XBRL. Given the extensive digital signature block and the nature of the content (which is not narrative text from a report, presentation, or transcript), it strongly suggests this is a wrapper or metadata associated with a formal filing. Since the content itself is the signature block and not the substantive report (like 10-K, IR, ER), and it doesn't fit specific categories like Director's Dealing (DIRS) or Dividend Notice (DIV), the most appropriate general category for a regulatory document identified primarily by its signature/metadata structure, especially when the actual content type is obscured by the signature block, is the general 'Regulatory Filings' fallback category (RNS). However, the presence of the XML structure and the digital signature itself is often associated with the submission of official SEC filings (like 10-K, 10-Q, etc.) or similar official regulatory submissions. Since the document length is very large (2.4 million characters), it is highly likely to be the full content of a major filing, even if the provided snippet is just the signature block. If this were an announcement (RPA), the text would typically be short and state that the report is attached. Since the text is massive and contains the signature block of what appears to be a complete document, it is more likely the filing itself. Without clear headers like 'FORM 10-K' or 'Earnings Release', classifying the exact type is difficult. But the presence of the XML signature block is common across many formal SEC filings. Given the ambiguity and the lack of specific report content, RNS (Regulatory Filings) remains the safest general classification for an unidentified, formally signed regulatory document structure. If I had to guess the underlying document type based on the sheer size and formality, it would lean towards 10-K or IR, but RNS is the best fit for an unidentifiable, signed regulatory artifact.
2024-04-19 Polish
1.5. Oświadczenie Zarządu JSF+SSF 2023
Board/Management Information Classification · 95% confidence The provided document text is extremely long (over 1.8 million characters) and appears to be the raw HTML/XML structure of a document, including extensive CSS styling and font definitions. The presence of complex HTML structure, especially with styling elements, suggests this is a rendered or source view of a comprehensive report, rather than a brief announcement. Given the massive size, it is highly unlikely to be a short announcement like an RPA or RNS. It must be one of the major, detailed reports (10-K, AR, IR). Since the text provided is only the beginning of the document structure (the head and style tags) and does not contain explicit section headers like "10-K," "Annual Report," or specific financial period disclosures (like 'For the Fiscal Year Ended December 31, 2023'), a definitive classification based on content keywords is impossible. However, the sheer volume of the source data strongly implies a comprehensive filing. In the absence of clear content, and considering the context of premium financial databases, the most common comprehensive annual filing is the 10-K. If the document were an IR (Interim Report), it would typically be shorter than a 10-K, but still substantial. Since we cannot confirm the content, we must rely on the structural evidence suggesting a full report. Given the ambiguity and the fact that the text is truncated and only shows boilerplate HTML/CSS, I will default to the most comprehensive annual filing type, 10-K, while acknowledging the low confidence due to lack of content confirmation. If this were a real-world scenario, I would request the full text or look for the first page content.
2024-04-19 Polish
Podpis
Regulatory Filings Classification · 95% confidence The provided document text consists almost entirely of XML structures, specifically related to digital signatures (xmlns:ds, SignatureValue, KeyInfo, X509Certificate, SignedProperties, etc.). This structure is characteristic of digitally signed regulatory filings or documents submitted electronically to regulatory bodies, often in the XBRL/iXBRL format. The document length is extremely large (17 million characters), indicating it is the full content of a substantial report, not just a short announcement. Since the content is the signed body of a document rather than an announcement *about* a document (which would trigger RPA/RNS based on the 'Menu vs Meal' rule), and given the complexity and regulatory nature implied by the digital signature block, this is most likely a comprehensive regulatory filing. However, the specific content of the underlying document (which is Base64 encoded in the Object tag) is not directly readable without decoding. In the context of standard SEC filings, a document containing extensive digital signature blocks and being very large is typically a primary report like a 10-K or an Interim Report (IR). Given the lack of explicit keywords like '10-K', 'Quarterly Report', or 'Annual Report' in the visible text, and the presence of a complex digital signature structure common to many official filings, the most appropriate classification among the comprehensive reports is either 10-K or IR. Since the document is massive and signed, it represents the core filing. Without further context or the ability to decode the payload, classifying it as a general comprehensive report is best. If this were an SEC filing, it would be a 10-K or 10-Q. Since 'IR' covers comprehensive interim reports, and '10-K' covers comprehensive annual reports, and this is clearly a full, signed document, I will lean towards the most comprehensive annual filing type if no period is specified, or the general comprehensive report type. Revisiting the definitions: 10-K is the 'Official yearly report'. IR is the 'Comprehensive financial report for a period shorter than a year'. Since the text itself gives no clue about the period, and the structure is purely technical (signatures), I will default to the most common comprehensive filing type that isn't explicitly quarterly, or use the general 'Regulatory Filing' (RNS) if the content is too ambiguous. However, the presence of a specific signing certificate (mentioning 'Krajowa Izba Rozliczeniowa S.A.' - Polish National Clearing House) suggests this might be a filing under Polish regulations, which often use XBRL/iXBRL structures similar to SEC filings. In the absence of specific keywords, and recognizing this is a full, signed document payload, it is a core report. I will classify it as '10-K' as the default for a large, comprehensive, signed financial document, acknowledging the high uncertainty regarding the exact period. *Self-Correction/Refinement*: Given the ambiguity and the fact that this is purely the signature block wrapping the actual data (which is encoded), this structure is often found in filings that are submitted via specific electronic portals. If it's not an ER, IR, or 10-K, it falls into the general regulatory category. Since it's a massive, complete document payload, it's not RPA. I will stick with the most comprehensive report type, 10-K, as the best fit for a large, signed financial document payload, but assign a moderate confidence due to the lack of textual content confirmation.
2024-04-19 Polish
1.4. Sprawozdanie na temat informacji niefinansowych Rainbow Tours SA 2023
Legal Proceedings Report Classification · 95% confidence The provided document text is extremely short (even though the metadata indicates a large total size, the visible text is truncated and appears to be HTML/CSS boilerplate for a document viewer, not the actual content of a financial report). The visible text contains only HTML structure, CSS styling, and font definitions, with no discernible financial keywords, regulatory headers (like 10-K, AR, ER), or reporting periods. Given the structure, this is likely the wrapper or container for a document that failed to load its primary content, or it is a very minimal announcement. Applying Rule 2 (The 'MENU VS MEAL' Rule): Since the visible text is essentially empty of content and does not describe the publication of a specific report, it cannot be classified as the report itself (like 10-K or IR). It also doesn't explicitly announce a report's publication. Given the lack of substantive content and the presence of generic HTML/CSS structure, the most appropriate fallback category is Regulatory Filings (RNS), as it serves as the general category for miscellaneous or unclassifiable filings, especially when the content is inaccessible or non-standard. However, since the document length metadata suggests a very large file (14,750,407 chars), it is highly probable that the actual content exists but was truncated before any meaningful text appeared. If we must classify based *only* on the visible, truncated text, RNS is the safest fallback. If we assume the underlying document is a standard filing that failed to render, we cannot determine the type. Sticking strictly to the visible text and the rules, RNS is the fallback.
2024-04-19 Polish
Podpis
Regulatory Filings Classification · 98% confidence The provided document text consists almost entirely of XML structures related to digital signatures ('Signatures', 'SignedInfo', 'SignatureValue', 'KeyInfo', 'X509Certificate', 'DigestValue', 'QualifyingProperties'). This format is characteristic of documents that have been digitally signed for authenticity and integrity, often required for official regulatory filings submitted electronically (like XBRL/iXBRL filings). Since the actual content of the report is Base64 encoded within the 'DigestValue' and 'Object' tags (and the decoded content appears to be an XHTML document structure, as indicated by 'Description: BINARY_FORMAT [XHTML]' and 'MimeType: text/plain'), this snippet is not the report itself (like 10-K or IR), but rather the wrapper or metadata confirming the signature of a larger document. Given the highly technical, signature-focused nature of the text, and the lack of specific financial reporting keywords (like 'Balance Sheet', 'Income Statement', 'MD&A', or specific fiscal periods), this is most likely a component of a regulatory submission. The presence of Polish certificate information ('Krajowa Izba Rozliczeniowa S.A.', 'PL') suggests a filing within the Polish regulatory environment. In the context of the provided classification codes, the most appropriate general category for a document component that confirms the integrity of a regulatory filing, especially when the primary content is obscured or encoded, is the general fallback category for regulatory announcements that don't fit specific report types: Regulatory Filings (RNS). If this were an announcement *about* a filing, RPA would be considered, but this looks like the signed payload itself, which falls under the general regulatory submission umbrella.
2024-04-19 Polish

Browse filings by year

11 years

Report missing filing

Can't find a specific document? Let us know and we'll add it within 24 hours.

We will notify you once the filing is added.
Report sent
Thank you. We will check the data and update it shortly.