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

ROMERIKE BETONGSAGING AS

Org. no. 979786506 Limited company (AS) Hurdal Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 150,000
Equity NOK 185,000
Incorporated 1998
Share capital NOK 100,000

ROMERIKE BETONGSAGING AS is registered as a limited company in Hurdal, Akershus with organisation number 979786506. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 1998. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Betongsaging, borring, asfaltsaging, innvendig riving, graving og utleie av minigraver.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 150,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 150,000
Equity
NOK 185,000
Est. value
NOK 539,000

Financial health · 2025

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

Who owns ROMERIKE BETONGSAGING AS?

OLE HERMAN SIGVARTSEN
ROMERIKE BETONGSAGING AS
NOK 1.3m rev. · NOK 150,000 profit

ROMERIKE BETONGSAGING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROMERIKE BETONGSAGING AS

Who owns ROMERIKE BETONGSAGING AS?

OLE HERMAN SIGVARTSEN is the largest registered owner, with 100.0%.

What is the revenue of ROMERIKE BETONGSAGING AS?

ROMERIKE BETONGSAGING AS had revenue of NOK 1.3m in 2025.

Who is the general manager of ROMERIKE BETONGSAGING AS?

Ole Herman Sigvartsen is registered as general manager of ROMERIKE BETONGSAGING AS.

Where is ROMERIKE BETONGSAGING AS based?

ROMERIKE BETONGSAGING AS has its business address in Hurdal.

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.