BIZTRAC BETA
Freight transport by road

MOSK AS

Org. no. 999167209 Limited company (AS) Eidsvoll Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 3,000
Operating profit NOK −694,000
Equity NOK 32.3m
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−694k kr).

MOSK AS is registered as a limited company in Eidsvoll, Akershus with organisation number 999167209. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investeringer i aksjer, verdipapirer, transport av gods og hest samt hva hermed står i forbindelse, herunder delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 3,000 in revenue and NOK −694,000 in operating profit.

Key figures · 2024

Revenue
NOK 3,000
Operating profit
NOK −694,000
Equity
NOK 32.3m
Est. value
NOK 24.1m

Financial health · 2024

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

Who owns MOSK AS?

MORTEN SKILLEBEKK
MOSK AS
NOK 3,000 rev. · NOK −694,000 profit

MOSK AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MOSK AS own?

MOSK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MOSK AS

Who owns MOSK AS?

MORTEN SKILLEBEKK is the largest registered owner, with 80.0%.

What is the revenue of MOSK AS?

MOSK AS had revenue of NOK 3,000 in 2024.

Who is the general manager of MOSK AS?

Morten Skillebekk is registered as general manager of MOSK AS.

Where is MOSK AS based?

MOSK AS has its business address in Eidsvoll Verk.

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.