Skip to main content
Feerum S.A. logo

Feerum S.A. — Investor Relations & Filings

Ticker · FEE ISIN · PLFEERM00018 LEI · 259400M78416GTXFYN23 WAR Manufacturing
Open in API
Filings indexed 587 across all filing types
Latest filing 2024-05-01 Audit Report / Informat…
Country PL Poland
Listing WAR FEE

About Feerum S.A.

http://feerum.pl/en/

Feerum S.A. is a manufacturer specializing in comprehensive solutions for the post-harvest management of agricultural products. The company designs, produces, and assembles integrated systems for drying, cleaning, conveying, and storing plant products, including grains, oily plants, and legumes. Its core product portfolio features grain silos, continuous flow dryers, and a range of transport equipment such as bucket elevators, chain conveyors, and belt conveyors. Feerum S.A. also provides automation systems and acts as a general contractor, delivering large-scale, turnkey drying and storage complexes. The company focuses on providing innovative and efficient solutions to ensure the optimal protection and safety of stored agricultural goods.

Recent filings

Filing Released Lang Actions
Roczne sprawozdanie finansowe FEERUM SA za 2023 rok
Audit Report / Information Classification · 1% confidence The document text provided is heavily truncated and consists almost entirely of HTML/CSS code, likely representing the structure and styling of a converted PDF file. The title tag within the head section reads: "FEERUM_SF_2023_2024-04-30_pl.xhtml". The presence of 'SF' (which often stands for 'Statutory Filing' or similar regulatory document) and a specific date (2024-04-30) suggests a formal financial report. Given the massive document length (6,547,130 characters), it is highly unlikely to be a short announcement (like RPA or RNS). The structure points towards a comprehensive filing. Since it is a formal filing with a specific date, and without explicit mention of 'Annual Report' (10-K) or 'Interim Report' (IR), the most appropriate classification for a comprehensive, dated statutory filing that isn't explicitly an Annual Report is the general 'Interim / Quarterly Report' (IR), or potentially a general 'Regulatory Filing' (RNS) if the content is too generic. However, the file name structure strongly suggests a formal, period-specific financial document. Given the context of financial reporting, and the lack of clear 10-K indicators, IR is a strong candidate for a comprehensive period report. If the document were confirmed to be the full annual filing, it would be 10-K. Since the content is unreadable HTML/CSS, I rely heavily on the filename convention. 'SF' often implies a statutory filing, which could be quarterly or annual. Given the ambiguity and the nature of the text being raw conversion output, I will lean towards the most comprehensive non-annual report category for a dated filing, which is IR, or the fallback RNS. Given the size, it's a report, not an announcement. I will classify it as an Interim Report (IR) based on the assumption that a large, dated filing that isn't explicitly annual is often quarterly/interim, but I acknowledge the high uncertainty due to the text content being unreadable structure. FY 2023
2024-05-01 Polish
Sprawozdanie Biegłego Rewidenta z badania JSF na dzień 31.12.2023_podpisy
Regulatory Filings Classification · 1% confidence The provided document text consists almost entirely of XML digital signature blocks (Signature, SignedInfo, KeyInfo, Object, QualifyingProperties, etc.). This structure is characteristic of a digitally signed document, often used for regulatory filings or official reports to ensure authenticity and integrity. The reference URI points to a file named "SzB_Feerum_2023-12-31_pl.xhtml", suggesting the underlying document relates to a financial entity ('Feerum') and a specific date (2023-12-31). Since the text itself is the signature wrapper and not the content of a financial report (like 10-K, IR, or ER), and it doesn't explicitly announce a report's publication (RPA), the most appropriate general classification for a digitally signed, non-standardized regulatory artifact is the fallback category, Regulatory Filings (RNS). The document length (6325 chars) is substantial enough to be the wrapper itself, not just a brief announcement.
2024-05-01 Polish
Sprawozdanie Biegłego Rewidenta z badania JSF na dzień 31.12.2023
Audit Report / Information Classification · 1% confidence The document text provided is primarily composed of HTML and CSS code, indicating it is a rendered or source view of a document converted from another format (likely PDF, given the `pdf2htmlEX` tool references in the CSS). The title tag contains 'SzB_Feerum_2023-12-31_pl.xhtml'. The presence of 'Feerum' and a specific date (2023-12-31) suggests a financial report or filing. However, the content itself is not the report narrative or structured data, but the underlying web rendering structure. Since the document is extremely long (1,148,110 chars) and appears to be a full conversion of a report rather than a short announcement linking to a report, it is likely the full content of a comprehensive filing. Given the Polish language context ('pl') and the lack of specific US SEC form identifiers (like 10-K, 10-Q), the most appropriate classification for a comprehensive, period-specific financial document that isn't explicitly an Annual Report (10-K) or Interim Report (IR) based on standard US definitions, but is clearly a full report, is often the general 'Interim / Quarterly Report' (IR) if the date suggests a period end, or the fallback 'Regulatory Filings' (RNS) if the exact nature is unclear. Given the structure and length, it represents the full content of a filing. Without explicit keywords like 'Balance Sheet' or 'Income Statement' in the visible text, and noting the date 2023-12-31 (year-end), it strongly suggests an Annual Report equivalent. However, since '10-K' is reserved for the official US filing, and this appears to be a foreign/non-SEC filing converted to HTML, the most fitting comprehensive category is 'Interim / Quarterly Report' (IR) if it's not the full annual report, or we must rely on the fallback. Given the length and the year-end date, it is most likely a full annual financial statement. If it were a short announcement, RPA would apply, but this is the full content. I will classify it as 'IR' (Interim/Quarterly Report) as a placeholder for a comprehensive period report, or 'RNS' as the safest fallback for non-standard formats, but since it's the full content, I lean towards the comprehensive report type. Let's re-evaluate based on the definitions: 10-K is 'Official yearly report'. If this 2023-12-31 document is the yearly report, 10-K is the best fit, assuming the definition covers equivalent annual reports globally, even if not filed on EDGAR as a 10-K. If it's a half-year report, IR applies. Given the year-end date, 10-K is the strongest conceptual match for a full annual performance document. I will use 10-K based on the year-end date implying a full annual report. FY 2023
2024-05-01 Polish
List Prezesa Zarządu_podpisy
Regulatory Filings Classification · 1% confidence The provided document text consists entirely of XML digital signature blocks (Signatures, SignedInfo, Reference, DigestValue, KeyInfo, X509Data, etc.). This structure is characteristic of an electronically signed document, often used for regulatory filings in European markets (indicated by Polish identifiers like 'PL' and 'Krajowa Izba Rozliczeniowa S.A.'). The references point to a file named 'FEERUM_LIST_PREZESA_2024-04-30_pl.xhtml'. The term 'LIST PREZESA' translates to 'President's List' or 'Management List'. Given the context of digital signatures and the reference to a list/document related to management/president, this is highly likely an official regulatory submission or a document related to governance/management information that requires formal electronic signing. Since the content is purely metadata about the signature and not the actual report content, and it references a specific document type ('LIST PREZESA'), it is most likely a Regulatory Filing (RNS) or potentially Governance Information (CGR) if the list pertains to board structure, but RNS is the safest general classification for an unsigned wrapper containing only signature metadata. However, upon reviewing the definitions, the content itself is the signature wrapper, not the report. If this wrapper is submitted as a standalone item, it falls under general Regulatory Filings (RNS). If the referenced document ('FEERUM_LIST_PREZESA') were available, it might fit better elsewhere (e.g., MANG or CGR). Given only the signature block, RNS is the most appropriate fallback for a generic regulatory submission wrapper.
2024-05-01 Polish
List Prezesa Zarządu
AGM Information Classification · 1% confidence The document text provided is an HTML structure containing CSS styling and font definitions, likely generated from converting a PDF file (indicated by the presence of 'pdf2htmlEX' in the CSS comments and the title 'FEERUM_LIST_PREZESA_2024-04-30_pl.xhtml'). The content itself is not the actual financial report or announcement text, but rather the underlying structure of a rendered document. Since the actual content (the 'meal') is missing, and we only have the container/wrapper structure, this strongly suggests the original source was a document that was published or announced. Given the lack of specific content keywords (like '10-K', 'Earnings', 'Dividend'), the most appropriate classification for a document wrapper or a generic regulatory output that doesn't fit a specific financial report type is the fallback category, 'Regulatory Filings' (RNS), or potentially 'Report Publication Announcement' (RPA) if we assume this HTML is the announcement itself. However, since the text is just the raw HTML/CSS structure of a converted file, and not a formal announcement text, classifying it as a generic 'Regulatory Filing' (RNS) is the safest fallback when the actual content is inaccessible or non-textual in this snippet.
2024-05-01 Polish
Zawarcie porozumienia przez spółkę zależną od Emitenta - Content (PL)
M&A Activity Classification · 1% confidence The document text is a formal announcement from the Management Board ('Zarząd') of Feerum S.A. regarding the receipt of a Memorandum of Understanding (MOU) with an Egyptian entity concerning a potential manufacturing plant investment in Egypt. This describes a significant business development, potential expansion, and a major transaction/agreement. This type of announcement, detailing strategic business moves, partnerships, or potential mergers/acquisitions, aligns best with the 'M&A Activity' (TAR) category if it were a takeover bid, or more generally, a significant corporate event. Since it details an intention to build a plant and secure land/lease, it relates to future business operations and strategic agreements. Given the options, it is a report about a significant business transaction/agreement that is not a standard financial report (10-K, IR, ER) or a director's dealing (DIRS). It is a report on a major strategic move, which often falls under M&A Activity (TAR) if it involves a joint venture or significant strategic partnership leading to a new facility, or sometimes under Regulatory Filings (RNS) if it's a mandatory disclosure of a major event. Because it explicitly details an agreement ('Memorandum of Understanding') regarding a major investment project and partnership, 'TAR' (M&A Activity/Takeover/Merger proposals) is the closest fit for a significant strategic transaction disclosure, although 'RNS' (Regulatory Filings) is a strong secondary candidate for mandatory disclosures of this nature. Given the nature of the MOU detailing a significant investment project and partnership, I will classify it as a significant corporate event disclosure, which often overlaps with M&A/Strategic Transaction reporting, leaning towards TAR as it involves a major business restructuring/expansion agreement.
2024-04-02 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.