BIZTRAC BETA
Uoppgitt

NOPPI HOLDING AS

Org. no. 931708910 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 10.1m
Operating profit NOK 6.5m
Equity NOK 5.1m
Incorporated 2023
Share capital NOK 30,000

NOPPI HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 931708910. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Forvaltning av skog og handel med tømmer, samt utvikling og deltakelse i fornybar kraft (energi basert på vind-, sol-, og vann). Kjøp, salg og forvaltning av aksjer, verdipapirer og fast eiendom, og hva som står i forbindelse, herunder eie selskaper som har slikt formål, samt selskap med andre formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.1m in revenue and NOK 6.5m in operating profit.

Key figures · 2024

Revenue
NOK 10.1m
Operating profit
NOK 6.5m
Equity
NOK 5.1m
Est. value
NOK 21.1m

Financial health · 2024

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

Who owns NOPPI HOLDING AS?

FREDRIK JACOB CARL MATHIESEN
NOPPI HOLDING AS
NOK 10.1m rev. · NOK 6.5m profit

NOPPI HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does NOPPI HOLDING AS own?

NOPPI HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NOPPI HOLDING AS

Who owns NOPPI HOLDING AS?

FREDRIK JACOB CARL MATHIESEN is the largest registered owner, with 33.3%.

What is the revenue of NOPPI HOLDING AS?

NOPPI HOLDING AS had revenue of NOK 10.1m in 2024.

Where is NOPPI HOLDING AS based?

NOPPI HOLDING AS has its business address in Oslo.

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.