BIZTRAC BETA
Other specialised construction activities n.e.c.

NARMO BETONGSAGING AS

Org. no. 971586966 Limited company (AS) Nordre Land Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 4.8m
Operating profit NOK −52,000
Equity NOK 1.8m
Incorporated 1994
Share capital NOK 100,000

Signals

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

NARMO BETONGSAGING AS is registered as a limited company in Nordre Land, Innlandet with organisation number 971586966. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 1994. Registered share capital is NOK 100,000. The company's stated purpose is: “Betongsaging og boring, sliping av betonggulv og virksomhet i tilknytning til dette. Selskapet kan videre eie og drive fast eiendom og kan likeledes ved aksjetegning eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.8m in revenue and NOK −52,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.8m
Operating profit
NOK −52,000
Equity
NOK 1.8m
Est. value
NOK 2.4m

Financial health · 2025

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

Who owns NARMO BETONGSAGING AS?

STEINAR ØVERLIER
NARMO BETONGSAGING AS
NOK 4.8m rev. · NOK −52,000 profit

NARMO BETONGSAGING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NARMO BETONGSAGING AS

Who owns NARMO BETONGSAGING AS?

STEINAR ØVERLIER is the largest registered owner, with 50.0%.

What is the revenue of NARMO BETONGSAGING AS?

NARMO BETONGSAGING AS had revenue of NOK 4.8m in 2025.

Where is NARMO BETONGSAGING AS based?

NARMO BETONGSAGING AS has its business address in Dokka.

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.