BIZTRAC BETA
Rental and operating of own or leased real estate

RUD-HAUGER NÆRINGSBYGG AS

Org. no. 993888567 Limited company (AS) Bærum Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 6.1m
Operating profit NOK 4.6m
Equity NOK 17.2m
Incorporated 2008
Share capital NOK 460,000

RUD-HAUGER NÆRINGSBYGG AS is registered as a limited company in Bærum, Akershus with organisation number 993888567. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 460,000, divided into 1000 shares. The company's stated purpose is: “Handel med, investering i og utleie av fast eiendom, samt handel med og investering i verdipapirer og andre formuesobjekter, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.1m in revenue and NOK 4.6m in operating profit.

Key figures · 2025

Revenue
NOK 6.1m
Operating profit
NOK 4.6m
Equity
NOK 17.2m
Est. value
NOK 21.8m

Financial health · 2025

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

Who owns RUD-HAUGER NÆRINGSBYGG AS?

BRUUN EIENDOM AS
RUD-HAUGER NÆRINGSBYGG AS
NOK 6.1m rev. · NOK 4.6m profit

RUD-HAUGER NÆRINGSBYGG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

RUD-HAUGER NÆRINGSBYGG AS er morselskap for 4 datterselskaper:

Frequently asked questions about RUD-HAUGER NÆRINGSBYGG AS

Who owns RUD-HAUGER NÆRINGSBYGG AS?

BRUUN EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of RUD-HAUGER NÆRINGSBYGG AS?

RUD-HAUGER NÆRINGSBYGG AS had revenue of NOK 6.1m in 2025.

Where is RUD-HAUGER NÆRINGSBYGG AS based?

RUD-HAUGER NÆRINGSBYGG AS has its business address in Rud.

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.