BIZTRAC BETA
Construction of residential and non-residential buildings

MASIV BYGG AS

Org. no. 943612226 Limited company (AS) Klepp Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 416.5m
Operating profit NOK 7.8m
Equity NOK 86.3m
Incorporated 1987
Employees 57
Share capital NOK 5.5m

Signals

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

MASIV BYGG AS is registered as a limited company in Klepp, Rogaland with organisation number 943612226. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1987 and has 57 registered employees. Registered share capital is NOK 5.5m, divided into 2600 shares. The company's stated purpose is: “Entreprenørvirksomhet innen bygg og anlegg, samt delta i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 416.5m in revenue and NOK 7.8m in operating profit.

Key figures · 2024

Revenue
NOK 416.5m
Operating profit
NOK 7.8m
Equity
NOK 86.3m
Est. value
NOK 68.8m

Financial health · 2024

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

Who owns MASIV BYGG AS?

MASIV AS
MASIV BYGG AS
NOK 416.5m rev. · NOK 7.8m profit

MASIV BYGG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MASIV BYGG AS own?

MASIV BYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MASIV BYGG AS

Who owns MASIV BYGG AS?

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

What is the revenue of MASIV BYGG AS?

MASIV BYGG AS had revenue of NOK 416.5m in 2024.

Where is MASIV BYGG AS based?

MASIV BYGG AS has its business address in Klepp Stasjon.

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.