biztrac. BETA
COMPANY REGISTER PROFILE
923547533 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

STARVHUSGATEN 2 B AS

Org. no. 923547533 Limited company (AS) Bergen Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 9.9m
Operating profit NOK 2.3m
Equity NOK 138.1m
Incorporated 2019
Share capital NOK 100,000

STARVHUSGATEN 2 B AS is registered as a limited company in Bergen, Vestland with organisation number 923547533. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie og drive fast eiendom samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.9m in revenue and NOK 2.3m in operating profit.

Key figures · 2025

Revenue
NOK 9.9m
▼ −19 %
Operating profit
NOK 2.3m
▼ −53 %
Equity
NOK 138.1m
▲ +0 %
Est. value
NOK 101.9m

Financial health · 2025

Liquidity
0.08
Not satisfactory
Current assets ÷ current liabilities
Profitability
1.8%
Weak
Return on total assets
Solidity
93.6%
Very good
Equity as a share of total capital

Who owns STARVHUSGATEN 2 B AS?

STARVHUSGATEN 2 B AS
NOK 9.9m rev. · NOK 2.3m profit

STARVHUSGATEN 2 B AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STARVHUSGATEN 2 B AS

Who owns STARVHUSGATEN 2 B AS?

DNB EIENDOMSHOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of STARVHUSGATEN 2 B AS?

STARVHUSGATEN 2 B AS had revenue of NOK 9.9m in 2025.

Who is the general manager of STARVHUSGATEN 2 B AS?

Lars Kristiansen is registered as general manager of STARVHUSGATEN 2 B AS.

Where is STARVHUSGATEN 2 B AS based?

STARVHUSGATEN 2 B AS has its business address in Bergen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.