BIZTRAC BETA
Rental and operating of own or leased real estate

BLEIVASSVEGEN 28A AS

Org. no. 885942482 Limited company (AS) Bergen Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK 1.7m
Equity NOK 7.5m
Incorporated 2003
Share capital NOK 2.7m

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-04-23 Adresseendring registrert 2026-04-23.

BLEIVASSVEGEN 28A AS is registered as a limited company in Bergen, Vestland with organisation number 885942482. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2003. Registered share capital is NOK 2.7m, divided into 8927 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK 1.7m in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK 1.7m
Equity
NOK 7.5m
Est. value
NOK 8.8m

Financial health · 2025

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

Who owns BLEIVASSVEGEN 28A AS?

ALIN INVEST AS
BLEIVASSVEGEN 28A AS
NOK 2.7m rev. · NOK 1.7m profit

BLEIVASSVEGEN 28A AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about BLEIVASSVEGEN 28A AS

Who owns BLEIVASSVEGEN 28A AS?

ALIN INVEST AS is the largest registered owner, with 90.1%.

What is the revenue of BLEIVASSVEGEN 28A AS?

BLEIVASSVEGEN 28A AS had revenue of NOK 2.7m in 2025.

Where is BLEIVASSVEGEN 28A AS based?

BLEIVASSVEGEN 28A AS has its business address in Kokstad.

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.