BIZTRAC BETA
Freight transport by road

MK TRANSPORT MOSS AS

Org. no. 923193839 Limited company (AS) Våler Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 44,000
Equity NOK 179,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-02-12 Adresseendring registrert 2026-02-12.

MK TRANSPORT MOSS AS is registered as a limited company in Våler, Østfold with organisation number 923193839. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Lastebiltransport på vei, anleggstransport og opplæring av lærlinger.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 44,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK 44,000
Equity
NOK 179,000
Est. value
NOK 220,000

Financial health · 2025

Liquidity
1.09
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.5%
Good
Equity as a share of total capital

Who owns MK TRANSPORT MOSS AS?

HENRIETTE MILLA FOLDVIK KARLSEN
MK TRANSPORT MOSS AS
NOK 2.1m rev. · NOK 44,000 profit

MK TRANSPORT MOSS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MK TRANSPORT MOSS AS

Who owns MK TRANSPORT MOSS AS?

HENRIETTE MILLA FOLDVIK KARLSEN is the largest registered owner, with 100.0%.

What is the revenue of MK TRANSPORT MOSS AS?

MK TRANSPORT MOSS AS had revenue of NOK 2.1m in 2025.

Who is the general manager of MK TRANSPORT MOSS AS?

Henriette Milla Foldvik Karlsen is registered as general manager of MK TRANSPORT MOSS AS.

Where is MK TRANSPORT MOSS AS based?

MK TRANSPORT MOSS AS has its business address in Våler I Østfold.

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.