BIZTRAC BETA
Construction of residential and non-residential buildings

ROMERIKE BYGG & BOLIG AS

Org. no. 994390651 Limited company (AS) Lunner Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 98,000
Equity NOK 131,000
Incorporated 2009
Share capital NOK 100,000

ROMERIKE BYGG & BOLIG AS is registered as a limited company in Lunner, Akershus with organisation number 994390651. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Tømrertjenester og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 98,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 98,000
Equity
NOK 131,000
Est. value
NOK 390,000

Financial health · 2024

Liquidity
1.10
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.9%
Good
Equity as a share of total capital

Who owns ROMERIKE BYGG & BOLIG AS?

TERJE AUKELI GUDBRANDSEN
ROMERIKE BYGG & BOLIG AS
NOK 1.8m rev. · NOK 98,000 profit

ROMERIKE BYGG & BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROMERIKE BYGG & BOLIG AS

Who owns ROMERIKE BYGG & BOLIG AS?

TERJE AUKELI GUDBRANDSEN is the largest registered owner, with 100.0%.

What is the revenue of ROMERIKE BYGG & BOLIG AS?

ROMERIKE BYGG & BOLIG AS had revenue of NOK 1.8m in 2024.

Who is the general manager of ROMERIKE BYGG & BOLIG AS?

Terje Aukeli Gudbrandsen is registered as general manager of ROMERIKE BYGG & BOLIG AS.

Where is ROMERIKE BYGG & BOLIG AS based?

ROMERIKE BYGG & BOLIG AS has its business address in Harestua.

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.