BIZTRAC BETA
Event catering activities

ML HANDEL AS

Org. no. 833155792 Limited company (AS) Ringerike Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 99,000
Equity NOK −62,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

ML HANDEL AS is registered as a limited company in Ringerike, Buskerud with organisation number 833155792. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby cateringtjenester, inkludert, men ikke begrenset til, forberedelse og levering av mat for ulike arrangementer som konferanser, bryllup, fester og bedriftsmøter.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 99,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 99,000
Equity
NOK −62,000
Est. value
NOK 492,000

Financial health · 2025

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

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

Who owns ML HANDEL AS?

MARITA LØNN
ML HANDEL AS
NOK 1.3m rev. · NOK 99,000 profit

ML HANDEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ML HANDEL AS

Who owns ML HANDEL AS?

MARITA LØNN is the largest registered owner, with 100.0%.

What is the revenue of ML HANDEL AS?

ML HANDEL AS had revenue of NOK 1.3m in 2025.

Who is the general manager of ML HANDEL AS?

Thea-Madelen Lønn is registered as general manager of ML HANDEL AS.

Where is ML HANDEL AS based?

ML HANDEL AS has its business address in Hønefoss.

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.