Skip to main content
Atende S.A. logo

Atende S.A. — Investor Relations & Filings

Ticker · ATD ISIN · PLATMSI00016 LEI · 259400CBBLICU7Q86X02 WAR Telecommunications, computer programming, consultancy, computing infrastructure, and other information service activities
Open in API
Filings indexed 557 across all filing types
Latest filing 2025-03-26 Regulatory Filings
Country PL Poland
Listing WAR ATD

About Atende S.A.

https://atende.pl/en

Atende S.A. is an information technology company that supports clients in their digital transformation. The company's core activities include the integration of complex ICT systems, cybersecurity, cloud services, and software development. Its offerings encompass building and managing computer networks and data centers, cloud migration, and comprehensive IT service management. Atende provides solutions for various sectors, with a significant focus on telecommunications, energy, and the public sector. The company also develops advanced cloud applications, AI and smart device solutions, and specialized platforms for Industry 4.0, including Smart Grid systems and utility billing applications.

Recent filings

Filing Released Lang Actions
Sprawozdanie z badania skonsolidowanego raportu rocznego Grupy Atende za 2024 r. - podpis
Regulatory Filings Classification · 95% confidence The document text consists almost entirely of XML structures related to digital signatures (Signature, SignedInfo, KeyInfo, X509Data, etc.). This structure is typical of filings that have been digitally signed for authenticity and integrity, often associated with regulatory submissions. Crucially, the text contains references to files like "SzB_SSF-2024-12-31-0-pl.xhtml" and mentions signing time (2025-03-26). The presence of a digital signature block, especially one referencing an external document (the actual content), strongly suggests this is a wrapper or metadata file accompanying a primary submission, rather than the primary report itself (like 10-K or IR). Since the content is not the report but the signature/metadata, and it doesn't fit specific categories like DIV, DIRS, or ER, the most appropriate fallback category for a general regulatory artifact that doesn't fit elsewhere is 'Regulatory Filings' (RNS). It is not an announcement of a report (RPA) because it is the signature block itself, not a brief announcement stating the report is attached.
2025-03-26 Polish
Sprawozdanie z badania skonsolidowanego raportu rocznego Grupy Atende za 2024 r.
Audit Report / Information Classification · 95% confidence The document text provided is an HTML structure containing CSS styling and metadata, specifically referencing 'Consolia XBRL Tools v2.11.7.5' and a title 'SzB_SSF-2024-12-31-0-pl.xhtml'. The presence of XBRL tools and an XHTML file extension strongly suggests this is a structured regulatory filing, likely related to financial reporting. Given the extensive length (over 2 million characters) and the technical nature of the content (XBRL processing), it is highly probable that this is a comprehensive financial report or a filing containing such data. Since it is not explicitly an Annual Report (10-K) or an Interim Report (IR) based on keywords, and it appears to be the raw data/structure of a filing, the most appropriate general category for structured financial data filings that don't fit the primary report types is 'Regulatory Filings' (RNS), or potentially 'Financial Supplement Data' (XLSX) if it were confirmed to be tabular data, but RNS is a safer fallback for raw regulatory submissions. However, the content structure itself, being an XHTML rendering of what is likely a regulatory submission (indicated by the XBRL context and the date '2024-12-31'), points towards a formal filing. Given the lack of specific report headers (like '10-K' or 'Quarterly Report'), and the technical nature, RNS is the best fit as a general regulatory submission category. FY 2024
2025-03-26 Polish
Oświadczenie Rady Nadzorczej Atende SA dotyczące komiteru audytu
Audit Report / Information Classification · 95% confidence The document text provided is an extensive HTML structure containing embedded CSS and what appears to be the raw content of a document, likely converted from a proprietary format (indicated by 'Aspose.Words for .NET 24.6.0' in the metadata). The content itself is highly detailed, featuring complex financial terminology, references to various operational and strategic elements, and a very large character count (73,975 chars). The structure and depth suggest a comprehensive report rather than a brief announcement. Key indicators like the sheer volume of text, the presence of detailed narrative, and the lack of explicit language stating that a report is merely 'attached' or 'published' (which would trigger the RPA/RNS rule) point towards a full, detailed filing. Given the definitions: - It is too long and detailed for a Fund Information/Factsheet (FS). - It is not explicitly an Earnings Release (ER) or Interim Report (IR) without seeing the specific headers, but its length suggests it could be one of the comprehensive reports. - It is not a Call Transcript (CT) as it lacks typical transcript formatting. Since the document is extremely long and detailed, it is most likely a comprehensive annual or interim report. Without explicit '10-K' or 'IR' headers, and given the general nature of the content (which seems to cover strategy, financials, and operations), the most appropriate classification for a very large, detailed corporate filing that isn't explicitly a proxy statement (DEF 14A) or an audit report (AR) is often the Annual Report (10-K) or Interim Report (IR). Given the massive size, 10-K is a strong candidate, but IR is also possible if it's a half-year report. Since the text is highly technical and voluminous, I will lean towards the most comprehensive yearly filing type, 10-K, as the default for large, detailed reports unless specific quarterly markers are present. However, since the text is heavily truncated and the content is generic technical data, classifying it as a comprehensive report is the goal. I will select 10-K as the best fit for a massive, detailed corporate document. Q2 2024
2025-03-26 Polish
Ocena Rady Nadzorczej sprawozdań rocznych Atende za 2024 r.
Audit Report / Information Classification · 95% confidence The document text provided is heavily truncated and appears to be the raw HTML/XML structure of a document, including font definitions and base64 encoded data, rather than the readable content of a financial filing. However, the presence of a very large character count (263,160 chars) suggests it is a comprehensive report, not a brief announcement. Since the actual content is inaccessible, I must rely on the metadata and the general structure. Given the context of financial reporting databases, a large, complex document structure often corresponds to a major filing like a 10-K or an Interim Report (IR). Without keywords, I cannot definitively choose between 10-K (Annual) or IR (Interim). Since the document length is substantial, I will lean towards a comprehensive report. If this were a real scenario, I would flag this as 'Unclassifiable Content' but must select from the provided list. Given the ambiguity, I will use the fallback 'Regulatory Filings' (RNS) as the safest general category for an unreadable, large filing, although '10-K' or 'IR' are statistically more likely for large documents. Q2 2024
2025-03-26 Polish
Informacja Zarządu Atende SA dotycząca wyboru firmy audytorskiej - podpis
Audit Report / Information Classification · 95% confidence The provided document text consists almost entirely of XML digital signature blocks ('Signature', 'SignedInfo', 'KeyInfo', 'QualifyingProperties'). The content within the signature references an external file named "Atende_Informacja_Zarzadu_Wybor_Audytora_do_Raportu_Rocznego_za_2024.xhtml". The Polish phrase "Informacja Zarządu Wybór Audytora do Raportu Rocznego" translates to "Management Information Selection of Auditor for the Annual Report". This strongly suggests the document is related to the selection of an auditor for the Annual Report, which falls under the scope of Audit Report/Information (AR) or potentially Governance Information (CGR) if it's about the board's decision process. However, since the core subject is the 'Auditor Selection for the Annual Report', the most fitting category is Audit Report / Information (AR), as it deals with the audit process/results, even if this specific snippet is just the signature block of the underlying document. FY 2024
2025-03-26 Polish
Informacja Zarządu Atende SA dotycząca wyboru firmy audytorskiej
Audit Report / Information Classification · 95% confidence The document text provided is an HTML structure containing embedded font data (WOFF) and extensive character sequences that strongly resemble a serialized, encoded, or compressed data stream, likely representing the full content of a document rather than a summary or announcement. Key indicators: 1. The document length is very large (89,556 characters). 2. The content is heavily encoded/serialized, containing base64 data within style tags and large blocks of binary-like data within 'xmpdf' or similar structures (implied by the structure and content of the character stream). 3. The presence of 'Aspose.Words for .NET 24.6.0' in the metadata suggests this is a conversion artifact of a complex document (like a PDF or DOCX) into an HTML wrapper. 4. The classification definitions do not have a specific category for raw, encoded document content or conversion artifacts. Given the massive size and the nature of the content (which appears to be the full, raw data of a report rather than a brief announcement), it is most likely the full Annual Report (10-K) or a comprehensive Interim Report (IR) that has been poorly rendered or converted into this format. Since the size is substantial and it contains complex data structures, it points towards a comprehensive filing. However, without clear headers like '10-K' or 'Consolidated Financial Statements', and given the highly technical, non-readable nature of the text, the safest classification for a large, complex, but unidentifiable regulatory document that doesn't fit the specific definitions (like ER, AR, IR) is the general fallback category for regulatory filings. Revisiting the definitions: - 10-K: Official yearly report. (Possible, but not explicitly named). - AR: Standalone audit reports. (Possible). - IR: Comprehensive financial report for a period shorter than a year. (Possible). Since the text is clearly a full document (not an announcement, ruling out RPA/RNS based on the 'Menu vs Meal' rule if it were short, but this is long), and it's too complex to definitively label as AR or IR without keywords, I will default to the most comprehensive annual filing if it were a standard report, or the general regulatory filing if it's just raw data. Given the sheer volume and the presence of encoded data suggesting a complete document structure, I will lean towards the most comprehensive report type, the Annual Report (10-K), as the most probable source document type, despite the lack of explicit headers in the provided snippet. *Self-Correction based on context:* The provided text is highly unusual and appears to be the raw, encoded content of a document, not the readable text of a filing. In a real-world scenario, this would be flagged for reprocessing. If forced to choose the *type* of document this raw data represents, the large size suggests a major filing. I will select 10-K as the most likely candidate for a very large, comprehensive filing, but assign a moderate confidence due to the corrupted/encoded nature of the text. *Final Decision:* The content is too garbled to confirm 10-K, AR, or IR. It is a large document, but the format is not standard. I will use the general Regulatory Filings (RNS) as the fallback for unclassifiable, large regulatory documents that don't match specific report types, as it is the most robust catch-all. Q2 2024
2025-03-26 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.