BIZTRAC BETA
Freight transport by road

MARTIN'S TRANSPORT AS

Org. no. 998015510 Limited company (AS) Nesodden Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 686,000
Equity NOK 1.3m
Incorporated 2012
Share capital NOK 30,000

MARTIN'S TRANSPORT AS is registered as a limited company in Nesodden, Akershus with organisation number 998015510. 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 300 shares. The company's stated purpose is: “Transport av varer og tjenester som faller inn under denne kategorien.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 686,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK 686,000
Equity
NOK 1.3m
Est. value
NOK 2.6m

Financial health · 2025

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

Who owns MARTIN'S TRANSPORT AS?

MARTIN FLATEBY
MARTIN'S TRANSPORT AS
NOK 2.3m rev. · NOK 686,000 profit

MARTIN'S TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MARTIN'S TRANSPORT AS own?

MARTIN'S TRANSPORT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MARTIN'S TRANSPORT AS

Who owns MARTIN'S TRANSPORT AS?

MARTIN FLATEBY is the largest registered owner, with 100.0%.

What is the revenue of MARTIN'S TRANSPORT AS?

MARTIN'S TRANSPORT AS had revenue of NOK 2.3m in 2025.

Who is the general manager of MARTIN'S TRANSPORT AS?

Martin Flateby is registered as general manager of MARTIN'S TRANSPORT AS.

Where is MARTIN'S TRANSPORT AS based?

MARTIN'S TRANSPORT AS has its business address in Nesodden.

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.