BIZTRAC BETA
Site preparation

FOSSUM & ISAKSEN AS

Org. no. 921664842 Limited company (AS) Indre Østfold Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 510,000
Equity NOK 1.8m
Incorporated 2018
Share capital NOK 70,000

FOSSUM & ISAKSEN AS is registered as a limited company in Indre Østfold, Østfold with organisation number 921664842. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2018. Registered share capital is NOK 70,000, divided into 70 shares. The company's stated purpose is: “Graving, transport, leiekjøring, vegetasjonsrydding, salg av varer tilknyttet virksomheten og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 510,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK 510,000
Equity
NOK 1.8m
Est. value
NOK 2.5m

Financial health · 2024

Liquidity
4.36
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
82.1%
Very good
Equity as a share of total capital

Who owns FOSSUM & ISAKSEN AS?

MIKAEL NADDUMSETER ISAKSEN
FOSSUM & ISAKSEN AS
NOK 2.2m rev. · NOK 510,000 profit

FOSSUM & ISAKSEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FOSSUM & ISAKSEN AS

Who owns FOSSUM & ISAKSEN AS?

MIKAEL NADDUMSETER ISAKSEN is the largest registered owner, with 50.0%.

What is the revenue of FOSSUM & ISAKSEN AS?

FOSSUM & ISAKSEN AS had revenue of NOK 2.2m in 2025.

Who is the general manager of FOSSUM & ISAKSEN AS?

Mikael Naddumseter Isaksen is registered as general manager of FOSSUM & ISAKSEN AS.

Where is FOSSUM & ISAKSEN AS based?

FOSSUM & ISAKSEN AS has its business address in Spydeberg.

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.