BIZTRAC BETA
Rental and operating of own or leased real estate

BRÅHOLMEN BOLIGUTLEIE AS

Org. no. 911717271 Limited company (AS) Namsos Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 324,000
Operating profit NOK 101,000
Equity NOK 664,000
Incorporated 2013
Share capital NOK 30,000

BRÅHOLMEN BOLIGUTLEIE AS is registered as a limited company in Namsos, Trøndelag with organisation number 911717271. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drive kjøp, salg og utleie av fast eiendom. Herunder å investere i aksjer og der til hørende aktivitet.”. The most recent filed accounts, for the 2025 financial year, show NOK 324,000 in revenue and NOK 101,000 in operating profit.

Key figures · 2025

Revenue
NOK 324,000
Operating profit
NOK 101,000
Equity
NOK 664,000
Est. value
NOK 723,000

Financial health · 2025

Liquidity
0.23
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.9%
Satisfactory
Equity as a share of total capital

Who owns BRÅHOLMEN BOLIGUTLEIE AS?

HARALD HANSEN
BRÅHOLMEN BOLIGUTLEIE AS
NOK 324,000 rev. · NOK 101,000 profit

BRÅHOLMEN BOLIGUTLEIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRÅHOLMEN BOLIGUTLEIE AS

Who owns BRÅHOLMEN BOLIGUTLEIE AS?

HARALD HANSEN is the largest registered owner, with 100.0%.

What is the revenue of BRÅHOLMEN BOLIGUTLEIE AS?

BRÅHOLMEN BOLIGUTLEIE AS had revenue of NOK 324,000 in 2025.

Who is the general manager of BRÅHOLMEN BOLIGUTLEIE AS?

Harald Hansen is registered as general manager of BRÅHOLMEN BOLIGUTLEIE AS.

Where is BRÅHOLMEN BOLIGUTLEIE AS based?

BRÅHOLMEN BOLIGUTLEIE AS has its business address in Namsos.

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.