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

K23 PROSJEKT B AS

Org. no. 919594349 Limited company (AS) Bergen Incorporated 2017 Active
Revenue 2025 NOK 335.4m
Operating profit NOK 75.0m
Equity NOK 22.7m
Incorporated 2017
Share capital NOK 30,000

K23 PROSJEKT B AS is registered as a limited company in Bergen, Vestland with organisation number 919594349. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Eie, drive og leie ut fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 335.4m in revenue and NOK 75.0m in operating profit.

Key figures · 2025

Revenue
NOK 335.4m
Operating profit
NOK 75.0m
▲ +1386 %
Equity
NOK 22.7m
▲ +333 %
Est. value
NOK 143.5m

Financial health · 2025

Liquidity
2.16
Very good
Current assets ÷ current liabilities
Profitability
27.3%
Very good
Return on total assets
Solidity
8.6%
Weak
Equity as a share of total capital

Who owns K23 PROSJEKT B AS?

K23 PROSJEKT B AS
NOK 335.4m rev. · NOK 75.0m profit

K23 PROSJEKT B AS has 1 registered shareholder:

All shareholders and roles →

Group structure

K23 PROSJEKT B AS er morselskap for 15 datterselskaper:

Frequently asked questions about K23 PROSJEKT B AS

Who owns K23 PROSJEKT B AS?

BRØDRENE ULVESETH EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of K23 PROSJEKT B AS?

K23 PROSJEKT B AS had revenue of NOK 335.4m in 2025.

Who is the general manager of K23 PROSJEKT B AS?

Anne Irene Ulveseth is registered as general manager of K23 PROSJEKT B AS.

Where is K23 PROSJEKT B AS based?

K23 PROSJEKT B AS has its business address in Godvik.

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.