BIZTRAC BETA
Rental and operating of own or leased real estate

BROKERUD EIENDOM AS

Org. no. 995167506 Limited company (AS) Lunner Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 610,000
Operating profit NOK 90,000
Equity NOK 601,000
Incorporated 2010
Share capital NOK 100,000

BROKERUD EIENDOM AS is registered as a limited company in Lunner, Akershus with organisation number 995167506. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Delta i andre selskaper, investere i verdipapirer og fast eiendom, utleie, gravearbeider, samt andre formål som naturlig hører inn under denne type virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 610,000 in revenue and NOK 90,000 in operating profit.

Key figures · 2024

Revenue
NOK 610,000
Operating profit
NOK 90,000
Equity
NOK 601,000
Est. value
NOK 568,000

Financial health · 2024

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

Who owns BROKERUD EIENDOM AS?

HADELAND & NITTEDAL - VVS AS
BROKERUD EIENDOM AS
NOK 610,000 rev. · NOK 90,000 profit

BROKERUD EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BROKERUD EIENDOM AS

Who owns BROKERUD EIENDOM AS?

HADELAND & NITTEDAL - VVS AS is the largest registered owner, with 100.0%.

What is the revenue of BROKERUD EIENDOM AS?

BROKERUD EIENDOM AS had revenue of NOK 610,000 in 2024.

Who is the general manager of BROKERUD EIENDOM AS?

Henning Brokerud is registered as general manager of BROKERUD EIENDOM AS.

Where is BROKERUD EIENDOM AS based?

BROKERUD EIENDOM AS has its business address in Roa.

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.