BIZTRAC BETA
Processing of tea and coffee

MØRKERE ENN MØRKEST AS

Org. no. 934823680 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 801,000
Operating profit NOK −21,000
Equity NOK 244,000
Incorporated 2025
Share capital NOK 280,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−21k kr).

MØRKERE ENN MØRKEST AS is registered as a limited company in Oslo, Oslo with organisation number 934823680. The business is classified under processing of tea and coffee (NACE 10.830). The company was incorporated in 2025. Registered share capital is NOK 280,000, divided into 280000 shares. The company's stated purpose is: “Kaffebrenning og salg av kaffe. Reparasjon og salg av kaffemaskiner og utstyr til kaffebrygging.”. The most recent filed accounts, for the 2025 financial year, show NOK 801,000 in revenue and NOK −21,000 in operating profit.

Key figures · 2025

Revenue
NOK 801,000
Operating profit
NOK −21,000
Equity
NOK 244,000
Est. value
NOK 559,000

Financial health · 2025

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

Who owns MØRKERE ENN MØRKEST AS?

CHRISTIAN MØRK
MØRKERE ENN MØRKEST AS
NOK 801,000 rev. · NOK −21,000 profit

MØRKERE ENN MØRKEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MØRKERE ENN MØRKEST AS

Who owns MØRKERE ENN MØRKEST AS?

CHRISTIAN MØRK is the largest registered owner, with 100.0%.

What is the revenue of MØRKERE ENN MØRKEST AS?

MØRKERE ENN MØRKEST AS had revenue of NOK 801,000 in 2025.

Who is the general manager of MØRKERE ENN MØRKEST AS?

Christian Mørk is registered as general manager of MØRKERE ENN MØRKEST AS.

Where is MØRKERE ENN MØRKEST AS based?

MØRKERE ENN MØRKEST 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.