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

ROMERIKE BETONGGULV AS

Org. no. 934046757 Limited company (AS) Ullensaker Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 13.3m
Operating profit NOK 1.7m
Equity NOK 2.1m
Incorporated 2024
Share capital NOK 30,000

ROMERIKE BETONGGULV AS is registered as a limited company in Ullensaker, Akershus with organisation number 934046757. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg av varer og tjenester, formidling av arbeid /logistikktjenester bygg og annleggsbransjen, rehabilitering betonggulv, støpearbeider. ”. The most recent filed accounts, for the 2024 financial year, show NOK 13.3m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 13.3m
Operating profit
NOK 1.7m
Equity
NOK 2.1m
Est. value
NOK 6.2m

Financial health · 2025

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

Who owns ROMERIKE BETONGGULV AS?

ELISABETH NILSEN
ROMERIKE BETONGGULV AS
NOK 13.3m rev. · NOK 1.7m profit

ROMERIKE BETONGGULV AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROMERIKE BETONGGULV AS

Who owns ROMERIKE BETONGGULV AS?

ELISABETH NILSEN is the largest registered owner, with 100.0%.

What is the revenue of ROMERIKE BETONGGULV AS?

ROMERIKE BETONGGULV AS had revenue of NOK 13.3m in 2024.

Who is the general manager of ROMERIKE BETONGGULV AS?

Bård Erik Nilsen is registered as general manager of ROMERIKE BETONGGULV AS.

Where is ROMERIKE BETONGGULV AS based?

ROMERIKE BETONGGULV AS has its business address in Jessheim.

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.