BIZTRAC BETA
Development of building projects

A: PROPERTY AS

Org. no. 922176868 Limited company (AS) Sykkylven Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 300,000
Operating profit NOK −362,000
Equity NOK −151,000
Incorporated 2018
Share capital NOK 60,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−151k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−362k kr).

A: PROPERTY AS is registered as a limited company in Sykkylven, Møre og Romsdal with organisation number 922176868. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2018. Registered share capital is NOK 60,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 300,000 in revenue and NOK −362,000 in operating profit.

Key figures · 2024

Revenue
NOK 300,000
Operating profit
NOK −362,000
Equity
NOK −151,000

Financial health · 2024

Liquidity
-0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-6.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns A: PROPERTY AS?

PEARSON SPECTER AS
A: PROPERTY AS
NOK 300,000 rev. · NOK −362,000 profit

A: PROPERTY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does A: PROPERTY AS own?

A: PROPERTY AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about A: PROPERTY AS

Who owns A: PROPERTY AS?

PEARSON SPECTER AS is the largest registered owner, with 100.0%.

What is the revenue of A: PROPERTY AS?

A: PROPERTY AS had revenue of NOK 300,000 in 2024.

Where is A: PROPERTY AS based?

A: PROPERTY AS has its business address in Sykkylven.

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.