BIZTRAC BETA
Rental and operating of own or leased real estate

BJORHAUGSLETTÅ 22 AS

Org. no. 990997446 Limited company (AS) Stavanger Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 4.2m
Operating profit NOK 2.5m
Equity NOK 18.4m
Incorporated 2007
Share capital NOK 1.3m

Signals

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

BJORHAUGSLETTÅ 22 AS is registered as a limited company in Stavanger, Rogaland with organisation number 990997446. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 1.3m, divided into 100 shares. The company's stated purpose is: “Utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.2m in revenue and NOK 2.5m in operating profit.

Key figures · 2024

Revenue
NOK 4.2m
Operating profit
NOK 2.5m
Equity
NOK 18.4m
Est. value
NOK 19.4m

Financial health · 2024

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

Who owns BJORHAUGSLETTÅ 22 AS?

VERKSGATEN 3 AS
BJORHAUGSLETTÅ 22 AS
NOK 4.2m rev. · NOK 2.5m profit

BJORHAUGSLETTÅ 22 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BJORHAUGSLETTÅ 22 AS

Who owns BJORHAUGSLETTÅ 22 AS?

VERKSGATEN 3 AS is the largest registered owner, with 100.0%.

What is the revenue of BJORHAUGSLETTÅ 22 AS?

BJORHAUGSLETTÅ 22 AS had revenue of NOK 4.2m in 2024.

Who is the general manager of BJORHAUGSLETTÅ 22 AS?

Albert Idsøe is registered as general manager of BJORHAUGSLETTÅ 22 AS.

Where is BJORHAUGSLETTÅ 22 AS based?

BJORHAUGSLETTÅ 22 AS has its business address in Stavanger.

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.