BIZTRAC BETA
Wholesale of other food

OLFACTUS AS

Org. no. 999297609 Limited company (AS) Larvik Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 210,000
Operating profit NOK 81,000
Equity NOK −16,000
Incorporated 2012
Share capital NOK 30,000

Signals

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

OLFACTUS AS is registered as a limited company in Larvik, Vestfold with organisation number 999297609. The business is classified under wholesale of other food (NACE 46.380). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Import og distribusjon av vin og mat samt tilhørende varer og tjenester. I tillegg vil selskapet foreta investeringer i selskaper med tilsvarende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 210,000 in revenue and NOK 81,000 in operating profit.

Key figures · 2025

Revenue
NOK 210,000
Operating profit
NOK 81,000
Equity
NOK −16,000
Est. value
NOK 381,000

Financial health · 2025

Liquidity
6.01
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-3.4%
Weak
Equity as a share of total capital

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

Who owns OLFACTUS AS?

CHRISTIAN MICHAEL BERG
OLFACTUS AS
NOK 210,000 rev. · NOK 81,000 profit

OLFACTUS AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about OLFACTUS AS

Who owns OLFACTUS AS?

CHRISTIAN MICHAEL BERG is the largest registered owner, with 25.0%.

What is the revenue of OLFACTUS AS?

OLFACTUS AS had revenue of NOK 210,000 in 2025.

Who is the general manager of OLFACTUS AS?

Christian Michael Berg is registered as general manager of OLFACTUS AS.

Where is OLFACTUS AS based?

OLFACTUS 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.