BIZTRAC BETA
Rental and operating of own or leased real estate

MK LAGER AS

Org. no. 926609432 Limited company (AS) Sandefjord Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 372,000
Operating profit NOK 145,000
Equity NOK −328,000
Incorporated 2021
Share capital NOK 100,000

Signals

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

MK LAGER AS is registered as a limited company in Sandefjord, Vestfold with organisation number 926609432. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og drift av fast eiendom og alt som står i forbindelse med dette, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 372,000 in revenue and NOK 145,000 in operating profit.

Key figures · 2025

Revenue
NOK 372,000
Operating profit
NOK 145,000
Equity
NOK −328,000
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
0.13
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-11.6%
Weak
Equity as a share of total capital

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

Who owns MK LAGER AS?

NYBORG-INVEST AS
MK LAGER AS
NOK 372,000 rev. · NOK 145,000 profit

MK LAGER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MK LAGER AS

Who owns MK LAGER AS?

NYBORG-INVEST AS is the largest registered owner, with 55.0%.

What is the revenue of MK LAGER AS?

MK LAGER AS had revenue of NOK 372,000 in 2025.

Who is the general manager of MK LAGER AS?

Marius Fevang is registered as general manager of MK LAGER AS.

Where is MK LAGER AS based?

MK LAGER AS has its business address in Andebu.

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.