biztrac. BETA
COMPANY REGISTER PROFILE
914879795 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Freight transport by road

ODLAND MASKIN AS

Org. no. 914879795 Limited company (AS) Samnanger Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 14.3m
Operating profit NOK −191,000
Equity NOK 1.7m
Incorporated 2015
Employees 8
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−191k kr).

ODLAND MASKIN AS is registered as a limited company in Samnanger, Vestland with organisation number 914879795. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2015 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Transport og entreprenørvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.3m in revenue and NOK −191,000 in operating profit.

Key figures · 2025

Revenue
NOK 14.3m
▼ −3 %
Operating profit
NOK −191,000
▼ −166 %
Equity
NOK 1.7m
▼ −1 %
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
1.60
Good
Current assets ÷ current liabilities
Profitability
-3.8%
Not satisfactory
Return on total assets
Solidity
37.7%
Good
Equity as a share of total capital

Who owns ODLAND MASKIN AS?

ODLAND MASKIN AS
NOK 14.3m rev. · NOK −191,000 profit

ODLAND MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ODLAND MASKIN AS

Who owns ODLAND MASKIN AS?

FOKO AS is the largest registered owner, with 100.0%.

What is the revenue of ODLAND MASKIN AS?

ODLAND MASKIN AS had revenue of NOK 14.3m in 2025.

Who is the general manager of ODLAND MASKIN AS?

Frode Odland is registered as general manager of ODLAND MASKIN AS.

Where is ODLAND MASKIN AS based?

ODLAND MASKIN AS has its business address in Tysse.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.