BIZTRAC BETA
Rental and operating of own or leased real estate

ÅSAMYRANE 165 AS

Org. no. 926149032 Limited company (AS) Bergen Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 691,000
Operating profit NOK −460,000
Equity NOK 1.3m
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−460k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ÅSAMYRANE 165 AS is registered as a limited company in Bergen, Vestland with organisation number 926149032. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Investere i fast eiendom eller andre selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 691,000 in revenue and NOK −460,000 in operating profit.

Key figures · 2024

Revenue
NOK 691,000
Operating profit
NOK −460,000
Equity
NOK 1.3m
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns ÅSAMYRANE 165 AS?

SPILLAN AS
ÅSAMYRANE 165 AS
NOK 691,000 rev. · NOK −460,000 profit

ÅSAMYRANE 165 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ÅSAMYRANE 165 AS

Who owns ÅSAMYRANE 165 AS?

SPILLAN AS is the largest registered owner, with 100.0%.

What is the revenue of ÅSAMYRANE 165 AS?

ÅSAMYRANE 165 AS had revenue of NOK 691,000 in 2024.

Where is ÅSAMYRANE 165 AS based?

ÅSAMYRANE 165 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.