Skip to main content
OPTeam S.A. logo

OPTeam S.A. — Investor Relations & Filings

Ticker · OPM ISIN · PLOPTEM00012 LEI · 259400YL67XC455VOK03 WAR Telecommunications, computer programming, consultancy, computing infrastructure, and other information service activities
Open in API
Filings indexed 471 across all filing types
Latest filing 2024-04-26 Audit Report / Informat…
Country PL Poland
Listing WAR OPM

About OPTeam S.A.

https://opteam.pl/en/

OPTeam S.A. is an information technology solutions provider specializing in the digitalization and automation of management processes for enterprises, universities, and public sector institutions. The company's core services include the implementation and maintenance of ERP systems, cybersecurity solutions, and IT infrastructure development. OPTeam S.A. also develops proprietary products, including the nAxiom low-code platform for creating applications and workflows, the web360 multiportal platform for building online portals, and the OPTiSync data integration bus. A key area of specialization is the higher education sector, where its OPTiCamp software supports electronic card systems, such as student IDs.

Recent filings

Filing Released Lang Actions
zal06_Ocena_Rady_OPTeam_ra_2024-04-26_pl.xhtml
Audit Report / Information Classification · 1% confidence The document text provided is extremely short (relative to the expected length of a full report like a 10-K or IR) and consists almost entirely of HTML structure, CSS styling, and metadata related to the rendering of a PDF file (indicated by 'pdf2htmlEX' in the styles and the title 'Raport'). There is no substantive financial content, regulatory headers (like '10-K', '10-Q', 'Proxy Statement'), or specific reporting periods mentioned in the visible text. This structure strongly suggests the document is an announcement or wrapper indicating that a report is available or has been published, rather than the report itself. Given the lack of specific content to classify it as AGM-R, ER, IR, etc., and the nature of the text being a container/wrapper, the most appropriate classification based on the 'MENU VS MEAL' rule is Report Publication Announcement (RPA) or the general fallback Regulatory Filing (RNS). Since it's clearly a wrapper for a document, RPA is slightly more specific if we assume the underlying document is a report. However, without any actual report content, RNS (General regulatory announcements/fallback) is also plausible. Given the context of financial filings, and the lack of specific content, I will default to the general regulatory filing category (RNS) as the content is purely structural metadata. Q3 2024
2024-04-26 Polish
zal02_Oswiadczenie_RN_OPTe_2024-04-26_pl.xhtml
Board/Management Information Classification · 1% confidence The document text provided is extremely short (despite the metadata indicating a large original file size, the visible text is minimal and appears to be HTML/CSS boilerplate from a PDF conversion tool like pdf2htmlEX). The visible content is dominated by HTML structure, CSS styling, and font definitions, with the title being 'Raport' (Report in Polish). Crucially, there is no substantive financial data, management discussion, or regulatory disclosure present in the visible snippet. Given the nature of the input (boilerplate/metadata wrapper) and the title 'Raport', this is most likely an announcement that a report is available or a placeholder for a document that failed to render fully. Following Rule #2 (The 'MENU VS MEAL' Rule), if the document is short and implies a report is attached or published, it should be classified as a Report Publication Announcement (RPA) or Regulatory Filing (RNS). Since 'RPA' is a specific category for announcing report publication, it is the most appropriate choice over the general fallback 'RNS' when the title suggests a report is the subject.
2024-04-26 Polish
zal08_Sprawozdanie_SFJ_OPT_2024-04-26_pl.xhtml.XAdES
Audit Report / Information Classification · 1% confidence The provided document text consists entirely of XML digital signature blocks (Signatures, SignedInfo, SignatureValue, KeyInfo, X509Certificate, etc.). These blocks are metadata used to verify the authenticity and integrity of an underlying document, not the content of a financial report itself. The references within the signatures point to a file named "Sprawozdanie_SFJ_OPT_2024-04-26_pl.xhtml". The presence of multiple signatures and the structure strongly suggest this is an attachment or a wrapper file containing only verification data for a primary report. Since the text does not contain the actual financial data, management discussion, or formal report structure, but rather the mechanism for verifying a report, it fits best under the general 'Regulatory Filings' category (RNS) as a supporting/metadata file, or potentially an 'Audit Report' (AR) if the underlying document is an audit report, but RNS is the safest fallback for non-content verification files. Given the context of financial reporting databases, a document composed solely of digital signatures verifying an external report (Sprawozdanie, which means 'Report' in Polish) is most appropriately classified as a general Regulatory Filing (RNS) or potentially an Audit Report (AR) if we assume the referenced file is an AR. However, since the document *itself* is just signatures, RNS is the most accurate classification for this specific payload. I will select RNS as the fallback for this signature-only metadata file. FY 2023
2024-04-26 Polish
zal03_Sprawozdanie_SFJ_OPT_2024-04-26_pl.xhtml
Audit Report / Information Classification · 1% confidence The document text provided is heavily truncated and appears to be the raw HTML/CSS structure generated by a PDF conversion tool (pdf2htmlEX), indicated by tags like `html`, `head`, `style`, and font definitions (`@font-face`). The title is simply "Raport" (Report in Polish). Crucially, the document length is extremely large (8,051,833 characters), suggesting it is the full content of a substantial report, not just a short announcement about one. Given the context of financial documents, a large, comprehensive report that is not explicitly identified as a 10-K (Annual Report) or IR (Interim Report) often falls into the category of a detailed financial statement or a comprehensive report. Since the text is Polish ("Raport") and the definitions are primarily English-based SEC/UK filings, we must look for the best fit among the comprehensive report types. The presence of a large body of text strongly suggests a full report rather than an announcement (RPA/RNS). Without specific keywords like '10-K', 'Quarterly', or 'Audit', the most appropriate classification for a large, comprehensive, but uncategorized report is often the general 'Audit Report / Information' (AR) if it contains detailed financials, or we must default to the most general comprehensive report type if the content is too obscured. However, given the sheer size and the generic title 'Report', and lacking specific quarterly/annual markers, classifying it as a comprehensive report is necessary. Since 'AR' is defined as 'Standalone audit reports, applied accounting principles, and results of internal or regulatory stress tests (excluding full Annual Reports)', and '10-K' is the full annual report, and 'IR' is the comprehensive interim report, the document is likely one of these. Given the ambiguity and the fact that it's a large document, I will lean towards the most comprehensive non-annual report category available, which is 'IR' (Interim / Quarterly Report), as it covers comprehensive reports shorter than a year, which is a common format for large regulatory filings outside the US annual cycle. If it were a US filing, the size would suggest 10-K, but the Polish language suggests a non-US filing. Without more context, 'IR' is a reasonable classification for a large, comprehensive report. Q3 2024
2024-04-26 Polish
zal07_Spr_Zarzadu_2023_OPT_2024-04-26_pl.xhtml.XAdES
Regulatory Filings Classification · 1% confidence The provided document text consists entirely of XML digital signature blocks ('Signature', 'SignedInfo', 'KeyInfo', 'X509Certificate', etc.). This structure is characteristic of a digitally signed document, often used for official regulatory filings in European markets (indicated by Polish issuer names like 'Krajowa Izba Rozliczeniowa S.A.' and Polish language references in the certificate data). The presence of multiple signatures and references to an XHTML file ('Spr_Zarzadu_2023_OPT_2024-04-26_pl.xhtml') suggests this is the signature wrapper for a primary document. Since the content is purely metadata/signature structure and not the report content itself, and given the context of corporate filings, this is most likely a general regulatory filing wrapper or an attachment that doesn't fit a specific financial report category. The fallback category 'Regulatory Filings' (RNS) is the most appropriate classification for such structural/metadata-heavy filings that don't contain the actual report narrative or financial tables.
2024-04-26 Polish
zal05_Spr_Zarzadu_2023_OPT_2024-04-26_pl.xhtml
Audit Report / Information Classification · 1% confidence The document text provided is extremely short (despite the metadata suggesting a large file size, the visible text is only HTML/CSS boilerplate from a PDF conversion tool, ending abruptly) and contains only the structure of an HTML document, including CSS styles for rendering a PDF. There is no discernible financial content, report title, regulatory header (like 10-K, AR, ER), or specific reporting period mentioned in the visible text. Given the lack of content and the nature of the text (conversion boilerplate), it cannot be classified as a specific financial report type (10-K, IR, ER, etc.). Therefore, the most appropriate classification is the general fallback category for miscellaneous or unclassifiable regulatory filings, which is 'RNS'. The confidence is low due to the lack of actual content. Q3 2024
2024-04-26 Polish

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.