BIZTRAC BETA
Construction of residential and non-residential buildings

PASLO EIENDOM AS

Org. no. 998434343 Limited company (AS) Ulvik Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 68,000
Operating profit NOK −99,000
Equity NOK 271,000
Incorporated 2012
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−99k kr).

PASLO EIENDOM AS is registered as a limited company in Ulvik, Vestland with organisation number 998434343. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Oppføring og salg av fast eiendom og utleie av fast eiendom, deltaglese i andre selskaper samt hva hermed hører til.”. The most recent filed accounts, for the 2024 financial year, show NOK 68,000 in revenue and NOK −99,000 in operating profit.

Key figures · 2024

Revenue
NOK 68,000
Operating profit
NOK −99,000
Equity
NOK 271,000
Est. value
NOK 278,000

Financial health · 2024

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

Who owns PASLO EIENDOM AS?

BJARNE ØYDVIN
PASLO EIENDOM AS
NOK 68,000 rev. · NOK −99,000 profit

PASLO EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PASLO EIENDOM AS

Who owns PASLO EIENDOM AS?

BJARNE ØYDVIN is the largest registered owner, with 100.0%.

What is the revenue of PASLO EIENDOM AS?

PASLO EIENDOM AS had revenue of NOK 68,000 in 2024.

Who is the general manager of PASLO EIENDOM AS?

Bjarne Øydvin is registered as general manager of PASLO EIENDOM AS.

Where is PASLO EIENDOM AS based?

PASLO EIENDOM AS has its business address in Ulvik.

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.