BIZTRAC BETA
Site preparation

FOLMER AS

Org. no. 923563857 Limited company (AS) Halden Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 2.6m
Operating profit NOK −734,000
Equity NOK 1.3m
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−734k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FOLMER AS is registered as a limited company in Halden, Østfold with organisation number 923563857. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Handel og tjenesteyting, som entreprenør innen graving, sveising, rørlegger, samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.6m in revenue and NOK −734,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.6m
Operating profit
NOK −734,000
Equity
NOK 1.3m
Est. value
NOK 879,000

Financial health · 2024

Liquidity
1.25
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.2%
Good
Equity as a share of total capital

Who owns FOLMER AS?

OSLOVEIEN EIENDOM AS
FOLMER AS
NOK 2.6m rev. · NOK −734,000 profit

FOLMER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOLMER AS

Who owns FOLMER AS?

OSLOVEIEN EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of FOLMER AS?

FOLMER AS had revenue of NOK 2.6m in 2024.

Who is the general manager of FOLMER AS?

Jon Bjørnar Folmer is registered as general manager of FOLMER AS.

Where is FOLMER AS based?

FOLMER AS has its business address in Berg I Østfold.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.