BIZTRAC BETA
Other real estate activities on a fee or contract basis

FOSSROCK AS

Org. no. 814305732 Limited company (AS) Tønsberg Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −13,000
Equity NOK 16.0m
Incorporated 2014
Share capital NOK 111,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−13k kr).

FOSSROCK AS is registered as a limited company in Tønsberg, Vestfold with organisation number 814305732. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2014. Registered share capital is NOK 111,000, divided into 111 shares. The company's stated purpose is: “Kjøp, salg og forvaltning av fast eiendom, kjøp og salg av aksjer, levere konsulenttjenester mot bygg og anleggsbransjen, kultur- og musikkoppdrag, samt dertil hørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 16.0m
Est. value
NOK 17.8m

Financial health · 2024

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

Who owns FOSSROCK AS?

KRISTOFFER FOSS
FOSSROCK AS
NOK 0 rev. · NOK −13,000 profit

FOSSROCK AS has 2 registered shareholders:

All shareholders and roles →

Which companies does FOSSROCK AS own?

FOSSROCK AS holds stakes in 12 companies:

See the full ownership structure →

Frequently asked questions about FOSSROCK AS

Who owns FOSSROCK AS?

KRISTOFFER FOSS is the largest registered owner, with 90.1%.

What is the revenue of FOSSROCK AS?

FOSSROCK AS had revenue of NOK 0 in 2024.

Where is FOSSROCK AS based?

FOSSROCK AS has its business address in Ramnes.

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.