BIZTRAC BETA
Wholesale of beverages

CHRYSOPIDAE AS

Org. no. 817753892 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 11.5m
Operating profit NOK 584,000
Equity NOK 77,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

CHRYSOPIDAE AS is registered as a limited company in Oslo, Oslo with organisation number 817753892. The business is classified under wholesale of beverages (NACE 46.340). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Engroshandel med vin og brennevin samt alt som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.5m in revenue and NOK 584,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.5m
Operating profit
NOK 584,000
Equity
NOK 77,000
Est. value
NOK 2.8m

Financial health · 2024

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.7%
Weak
Equity as a share of total capital

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

Who owns CHRYSOPIDAE AS?

NATURAL SELECTIONS AS
CHRYSOPIDAE AS
NOK 11.5m rev. · NOK 584,000 profit

CHRYSOPIDAE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CHRYSOPIDAE AS

Who owns CHRYSOPIDAE AS?

NATURAL SELECTIONS AS is the largest registered owner, with 100.0%.

What is the revenue of CHRYSOPIDAE AS?

CHRYSOPIDAE AS had revenue of NOK 11.5m in 2024.

Who is the general manager of CHRYSOPIDAE AS?

Terje Nordrik Meling-Lorntzen is registered as general manager of CHRYSOPIDAE AS.

Where is CHRYSOPIDAE AS based?

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