BIZTRAC BETA
Rental and operating of own or leased real estate

BRUGATA 19 AS

Org. no. 923558160 Limited company (AS) Bergen Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 139.5m
Operating profit NOK 124.5m
Equity NOK 5.2m
Incorporated 2019
Share capital NOK 150,000

Signals

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

BRUGATA 19 AS is registered as a limited company in Bergen, Vestland with organisation number 923558160. 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 150,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 2024 financial year, show NOK 139.5m in revenue and NOK 124.5m in operating profit.

Key figures · 2024

Revenue
NOK 139.5m
Operating profit
NOK 124.5m
Equity
NOK 5.2m
Est. value
NOK 227.9m

Financial health · 2024

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

Who owns BRUGATA 19 AS?

DNB EIENDOMSHOLDING AS
BRUGATA 19 AS
NOK 139.5m rev. · NOK 124.5m profit

BRUGATA 19 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRUGATA 19 AS

Who owns BRUGATA 19 AS?

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

What is the revenue of BRUGATA 19 AS?

BRUGATA 19 AS had revenue of NOK 139.5m in 2024.

Who is the general manager of BRUGATA 19 AS?

Lars Kristiansen is registered as general manager of BRUGATA 19 AS.

Where is BRUGATA 19 AS based?

BRUGATA 19 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 15.06.2026.

Report a problem

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