BIZTRAC BETA
Rental and operating of own or leased real estate

NILBYGG AS

Org. no. 999286844 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 7.5m
Operating profit NOK 3.3m
Equity NOK 101.2m
Incorporated 2012
Share capital NOK 2.6m

Signals

1 flags
  • Nylig endring 2026-02-12 Adresseendring registrert 2026-02-12.

NILBYGG AS is registered as a limited company in Oslo, Oslo with organisation number 999286844. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 2.6m, divided into 25512 shares. The company's stated purpose is: “Drift, kjøp, salg, bestyrelse og bebyggelse av fast eiendom, deltagelse i andre selskaper og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.5m in revenue and NOK 3.3m in operating profit.

Key figures · 2024

Revenue
NOK 7.5m
Operating profit
NOK 3.3m
Equity
NOK 101.2m
Est. value
NOK 78.6m

Financial health · 2024

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

Who owns NILBYGG AS?

ISABEL AS
NILBYGG AS
NOK 7.5m rev. · NOK 3.3m profit

NILBYGG AS has 4 registered shareholders:

All shareholders and roles →

Which companies does NILBYGG AS own?

NILBYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NILBYGG AS

Who owns NILBYGG AS?

ISABEL AS is the largest registered owner, with 50.0%.

What is the revenue of NILBYGG AS?

NILBYGG AS had revenue of NOK 7.5m in 2024.

Who is the general manager of NILBYGG AS?

Hans Preben Gulbrandsen is registered as general manager of NILBYGG AS.

Where is NILBYGG AS based?

NILBYGG AS has its business address in Oslo.

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.