BIZTRAC BETA
Rental and operating of own or leased real estate

BODØ BOLIGUTLEIE AS

Org. no. 888390642 Limited company (AS) Fauske Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 935,000
Equity NOK 1.6m
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BODØ BOLIGUTLEIE AS is registered as a limited company in Fauske, Nordland with organisation number 888390642. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift og utleie av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 935,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 935,000
Equity
NOK 1.6m
Est. value
NOK 3.1m

Financial health · 2024

Liquidity
0.69
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.1%
Good
Equity as a share of total capital

Who owns BODØ BOLIGUTLEIE AS?

CROAB HOLDING AS
BODØ BOLIGUTLEIE AS
NOK 2.2m rev. · NOK 935,000 profit

BODØ BOLIGUTLEIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BODØ BOLIGUTLEIE AS

Who owns BODØ BOLIGUTLEIE AS?

CROAB HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BODØ BOLIGUTLEIE AS?

BODØ BOLIGUTLEIE AS had revenue of NOK 2.2m in 2024.

Who is the general manager of BODØ BOLIGUTLEIE AS?

Christer Robertsen is registered as general manager of BODØ BOLIGUTLEIE AS.

Where is BODØ BOLIGUTLEIE AS based?

BODØ BOLIGUTLEIE AS has its business address in Valnesfjord.

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.