Skip to main content
Spyrosoft S.A. logo

Spyrosoft S.A. — Investor Relations & Filings

Ticker · SPR ISIN · PLSPRSF00011 LEI · 259400S74NHLG59KC394 WAR Telecommunications, computer programming, consultancy, computing infrastructure, and other information service activities
Open in API
Filings indexed 346 across all filing types
Latest filing 2025-04-24 Regulatory Filings
Country PL Poland
Listing WAR SPR

About Spyrosoft S.A.

https://spyro-soft.com/

Spyrosoft is a software engineering and technology consulting company that provides bespoke software solutions and IT strategy services. The company guides clients through digital transformation, from initial product concept and technology selection to the development of market-ready solutions. Core service areas include artificial intelligence and machine learning (AI/ML), cloud computing, cybersecurity, embedded systems, and Human-Machine Interface (HMI) development. Spyrosoft also offers expertise in ecommerce platforms, Salesforce integration, and mobile application development, with a focus on UX/UI design and performance optimization. The company deploys multidisciplinary teams to deliver tailored solutions across various sectors, including automotive, finance, HR Tech, and EduTech. They specialize in developing technology for Industry 4.0 applications, assisting clients in navigating complex technical challenges.

Recent filings

Filing Released Lang Actions
SPR_RN_KA
Regulatory Filings Classification · 1% confidence The document text provided is heavily dominated by HTML/CSS code, indicating it is a rendered or converted file, likely from a PDF, as suggested by the CSS comments referencing 'pdf2htmlEX'. The title tag contains 'SPR_RN_KA-2024-12-31-0-pl.xhtml'. The presence of 'RN' (Regulatory Notice/Report) and the structure strongly suggest this is a regulatory filing that has been converted to HTML. Given the extensive length (137,442 chars) and the nature of regulatory filings often being comprehensive reports, it is unlikely to be a short announcement (RPA/RNS) unless the content itself is the full report. Since the content is not visible but the metadata suggests a large document converted from a source format, and the title hints at a regulatory filing ('RN'), the most appropriate classification among the provided options for a comprehensive regulatory document is either 10-K (Annual Report) or IR (Interim/Quarterly Report). However, without explicit keywords like '10-K', 'Annual Report', or specific financial period disclosures (like 'Q1', 'Half Year'), and given the generic 'RN' in the title, the safest classification for a general regulatory filing that isn't clearly an annual report or quarterly report is the fallback category for miscellaneous regulatory announcements, RNS, or if it's a known report type, we must infer. Since the document is very long, it is a full report, not just an announcement. Given the lack of specific period indicators, and assuming 'RN' stands for Regulatory Notice/Report, RNS (Regulatory Filings) is the best fit as a general regulatory document that doesn't fit the specific report types (10-K, IR). If this were a known mandatory filing, 10-K or IR would be better, but RNS covers general regulatory announcements.
2025-04-24 Polish
SPR_RN_audytor
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), as indicated by the presence of extensive CSS styling, font definitions (woff data), and structural tags like 'html', 'head', 'title', and 'style'. The title tag contains 'SPR_RN_audytor-2024-12-31-0-pl.xhtml'. The presence of 'audytor' (auditor in Polish) and a specific date (2024-12-31) strongly suggests this is an Audit Report or related information. Since the document is not the full Annual Report (10-K) but specifically mentions an auditor and a date, the most appropriate classification is Audit Report / Information (AR). The document length is substantial (170k chars), suggesting it contains the full content, not just an announcement. FY 2024
2025-04-24 Polish
SPR_JSF
Regulatory Filings Classification · 1% confidence The document text consists almost entirely of XML structures containing digital signatures, certificates (X509Data), and signed properties (SignedProperties, SigningTime, DigestValue). The presence of multiple 'Signature' blocks and references to files like 'SPR_JSF-2024-12-31-0-pl.xhtml' strongly indicates this is a digitally signed document wrapper, likely an attachment or the core structure of a regulatory filing. Key indicators: 1. Extensive use of XML Digital Signature (ds:) and XML Advanced Electronic Signatures (xades:) namespaces. 2. Presence of 'SigningTime' (e.g., 2025-04-24T04:53:03Z) and certificate information. 3. The document length is 43,310 characters, which is substantial, suggesting it contains the content being signed, not just a brief announcement. 4. The reference URI mentions 'SPR_JSF-2024-12-31-0-pl.xhtml' and a date '2024-12-31', suggesting a report for the year-end 2024. Given the structure is the signature block itself, and it references an underlying document related to a specific period (2024-12-31), this is most likely the signed version of a comprehensive report. Since the document is long and contains detailed signing information, it is not a simple 'Report Publication Announcement' (RPA). We must determine if it's an Annual Report (10-K) or an Interim Report (IR). The date '2024-12-31' strongly suggests a year-end filing. While the text doesn't explicitly say '10-K', the year-end nature points towards the Annual Report category, or potentially a comprehensive Audit Report (AR) if it were explicitly labeled as such. However, in the context of standard SEC filings, a year-end document is typically a 10-K. Since the content is the signature wrapper, and we cannot definitively confirm the full content type, we look for the most encompassing category for a comprehensive annual filing. If this were a standard SEC filing, the 10-K would be the primary candidate for a year-end report. However, the presence of Polish/European certificate issuers ('Certum', 'PL') and Polish text snippets ('Opis formatu dokumentu oraz jego pełna nazwa') suggests this might be a local regulatory filing rather than a US SEC 10-K. Without explicit keywords like '10-K', 'Annual Report', or 'Financial Statements', the safest classification for a comprehensive, signed, year-end document that doesn't fit other specific categories (like ER, IR, or DIV) is the general 'Regulatory Filings' (RNS) or, if we assume it's the full annual report, '10-K'. Given the structure is the signature block, and it's not a US SEC filing format, 'RNS' (General regulatory announcements/fallback) is a strong possibility. Revisiting the definitions: '10-K' is for the official yearly report. 'AR' is for standalone audit reports. Since this is a signed document wrapper for a year-end file, and it's not a brief announcement, it represents the filing itself. Given the year-end date (2024-12-31), I will classify it as the most likely comprehensive annual report type, 10-K, acknowledging the non-US context might make RNS technically more accurate if 10-K is strictly US-SEC defined. Given the high confidence in it being a full, signed report, 10-K is the best fit for a comprehensive annual document. *Self-Correction based on context*: The document is clearly a digitally signed XML file wrapper. This format is common for various regulatory submissions globally. Since the underlying file is dated 2024-12-31 (year-end), it represents a full annual filing. I will stick with 10-K as the classification for a full annual report, as it is the most specific category for year-end comprehensive data, even if the wrapper format is unusual for a typical EDGAR 10-K submission. Confidence is high that it is a full report wrapper, but moderate on the exact type (10-K vs AR vs RNS) due to non-US context.
2025-04-24 Polish
SPR_JSF
Audit Report / Information Classification · 1% confidence The document text provided is an HTML structure containing CSS styling and metadata, which is characteristic of a document that has been converted from a PDF format (indicated by the presence of 'pdf2htmlEX' in the CSS comments and the title 'SPR_JSF-2024-12-31-0-pl.xhtml'). The content itself is highly technical, related to font embedding and layout, and does not contain substantive financial reporting language (like 'balance sheet', 'income statement', 'MD&A', or specific filing headers like '10-K' or 'DEF 14A'). The filename 'SPR_JSF-2024-12-31-0-pl.xhtml' suggests a filing related to a specific date (2024-12-31) and potentially a specific type of report ('SPR' or similar), but without the actual content, it's impossible to classify it as a specific report type (like 10-K or IR). Given the lack of recognizable content and the nature of the provided text (a converted document structure), the most appropriate fallback category is 'Regulatory Filings' (RNS), as it covers miscellaneous or unclassifiable regulatory documents, or potentially 'XLSX' if this was intended to be supplementary data, but RNS is safer for unknown formats. However, upon closer inspection of the definitions, none perfectly fit a raw HTML/CSS conversion artifact. Since this is clearly a container/wrapper for a document rather than the document itself, and it doesn't announce a report (RPA), the best fit among the provided codes for an unidentified regulatory document structure is RNS (Regulatory Filings) as a general catch-all for non-standard submissions. FY 2024
2025-04-24 Polish
SPR_raport
Regulatory Filings Classification · 1% confidence The provided document text consists entirely of XML digital signature blocks (Signatures, SignedInfo, SignatureValue, KeyInfo, Object, QualifyingProperties). This structure is characteristic of an XML-based regulatory filing that has been digitally signed for authenticity, often seen in XBRL or other structured data submissions to regulatory bodies. The content itself does not describe financial results, management changes, or meeting details. Since the content is purely technical metadata related to the signing of a document (which references 'RaportSPYR-2024-12-31-0-pl.xhtml'), and it does not contain the actual report content, it is most appropriately classified as a general Regulatory Filing (RNS) or potentially a Financial Supplement Data (XLSX) if the underlying signed object was a data file, but RNS is the safer general category for raw, signed metadata blocks that don't fit specific report types. Given the lack of descriptive financial or corporate action text, RNS is the best fit as a fallback for technical regulatory artifacts.
2025-04-24 Polish
SPR_raport
Audit Report / Information Classification · 1% confidence The document text provided is an HTML structure containing CSS styling and font definitions, generated by a tool called 'pdf2htmlEX'. The title tag reads 'RaportSPYR-2024-12-31-0-pl.xhtml'. The presence of 'Raport' (Report in Polish) and a specific date (2024-12-31) suggests this is a financial report, likely an annual or interim one. However, the content itself is not the report data but the HTML wrapper used to display the converted PDF. Given the extremely large document length (3,955,704 chars) and the fact that the provided text is just the header/styling of the converted file, this strongly suggests the original document was a comprehensive report. Since the filename contains 'Raport' and a year-end date (12-31), it is most likely an Annual Report (10-K equivalent for the local jurisdiction) or an Interim Report (IR). Without seeing the actual content, classifying it as the report itself (10-K or IR) is risky based only on the wrapper. However, the 'Menu vs Meal' rule suggests that if the document is the report, we classify it as such. Given the context of financial reporting databases, a file named 'RaportSPYR-2024-12-31' is overwhelmingly likely to be the full Annual Report (10-K) or a comprehensive Interim Report (IR). Since 12-31 is a common year-end date, I lean towards the Annual Report (10-K) or a comprehensive Polish equivalent. If it were just an announcement, the text would be much shorter and explicitly state the report is attached (Rule 2). Since the text provided is the *content* of the converted file (even if it's just the wrapper), I will classify it as the most comprehensive yearly report type available, which is 10-K, or the closest equivalent for comprehensive reports, IR. Given the structure and length, it is the report itself, not an announcement. I will select IR as it is a general comprehensive report, though 10-K is also plausible for a year-end filing. FY 2024
2025-04-24 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.