BIZTRAC BETA
Publishing of newspapers

PARC FERMÉ AS

Org. no. 922321140 Limited company (AS) Larvik Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 132,000
Equity NOK −179,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−179k kr).

PARC FERMÉ AS is registered as a limited company in Larvik, Vestfold with organisation number 922321140. The business is classified under publishing of newspapers (NACE 58.120). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100000 shares. The company's stated purpose is: “Å drifte nettavis med fokus på norsk og internasjonal bilsport, salg av bilder og andre multimediatjenester samt rådgivningstjenester i tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 132,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 132,000
Equity
NOK −179,000
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
0.29
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-101.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns PARC FERMÉ AS?

SIMEDIA AS
PARC FERMÉ AS
NOK 1.8m rev. · NOK 132,000 profit

PARC FERMÉ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PARC FERMÉ AS

Who owns PARC FERMÉ AS?

SIMEDIA AS is the largest registered owner, with 100.0%.

What is the revenue of PARC FERMÉ AS?

PARC FERMÉ AS had revenue of NOK 1.8m in 2025.

Who is the general manager of PARC FERMÉ AS?

Simen Næss Hagen is registered as general manager of PARC FERMÉ AS.

Where is PARC FERMÉ AS based?

PARC FERMÉ AS has its business address in Larvik.

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.