BIZTRAC BETA
Site preparation

NORDBØ MASKIN AS

Org. no. 912628930 Limited company (AS) Kvitsøy Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 331.9m
Operating profit NOK 22.0m
Equity NOK 56.1m
Incorporated 2013
Employees 158
Share capital NOK 12.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

NORDBØ MASKIN AS is registered as a limited company in Kvitsøy, Rogaland with organisation number 912628930. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2013 and has 158 registered employees. Registered share capital is NOK 12.0m, divided into 12000 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendommer, handel med aksjer og andre verdipapirer. Entreprenørvirksomhet og hva med der står i forbindelse. Yte tjenester til egne datterselskaper/konsern. Rådgivning samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 331.9m in revenue and NOK 22.0m in operating profit.

Key figures · 2024

Revenue
NOK 331.9m
Operating profit
NOK 22.0m
Equity
NOK 56.1m
Est. value
NOK 101.5m

Financial health · 2024

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

Who owns NORDBØ MASKIN AS?

NORDBØ AS
NORDBØ MASKIN AS
NOK 331.9m rev. · NOK 22.0m profit

NORDBØ MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORDBØ MASKIN AS

Who owns NORDBØ MASKIN AS?

NORDBØ AS is the largest registered owner, with 100.0%.

What is the revenue of NORDBØ MASKIN AS?

NORDBØ MASKIN AS had revenue of NOK 331.9m in 2024.

Where is NORDBØ MASKIN AS based?

NORDBØ MASKIN AS has its business address in Kvitsøy.

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.