BIZTRAC BETA
Rental and operating of own or leased real estate

PERLO AS

Org. no. 914749689 Limited company (AS) Kvinnherad Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 133,000
Operating profit NOK −48,000
Equity NOK 998,000
Incorporated 2014
Share capital NOK 900,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−48k kr).
  • Nylig endring 2026-07-21 Adresseendring registrert 2026-07-21.

PERLO AS is registered as a limited company in Kvinnherad, Vestland with organisation number 914749689. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 900,000, divided into 900 shares. The company's stated purpose is: “Utvikle, utleie, omsette og drifte fast eiendom. Selskap kan videre delta i supplerende eller lignende virksomhet og hva som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 133,000 in revenue and NOK −48,000 in operating profit.

Key figures · 2024

Revenue
NOK 133,000
Operating profit
NOK −48,000
Equity
NOK 998,000
Est. value
NOK 828,000

Financial health · 2024

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

Who owns PERLO AS?

MECON AS
PERLO AS
NOK 133,000 rev. · NOK −48,000 profit

PERLO AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about PERLO AS

Who owns PERLO AS?

MECON AS is the largest registered owner, with 33.3%.

What is the revenue of PERLO AS?

PERLO AS had revenue of NOK 133,000 in 2024.

Who is the general manager of PERLO AS?

Dag Handeland is registered as general manager of PERLO AS.

Where is PERLO AS based?

PERLO AS has its business address in Sæbøvik.

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.