BIZTRAC BETA
Rental and operating of own or leased real estate

PRENTE.NO AS

Org. no. 916162952 Limited company (AS) Gloppen Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 60,000
Operating profit NOK −17,000
Equity NOK 63,000
Incorporated 2015
Share capital NOK 100,000

Signals

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

PRENTE.NO AS is registered as a limited company in Gloppen, Vestland with organisation number 916162952. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Drive investering i andre selskap samt sal av administrasjonstenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 60,000 in revenue and NOK −17,000 in operating profit.

Key figures · 2024

Revenue
NOK 60,000
Operating profit
NOK −17,000
Equity
NOK 63,000
Est. value
NOK 134,000

Financial health · 2024

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

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

Who owns PRENTE.NO AS?

OLAV AABREKK
PRENTE.NO AS
NOK 60,000 rev. · NOK −17,000 profit

PRENTE.NO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PRENTE.NO AS own?

PRENTE.NO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about PRENTE.NO AS

Who owns PRENTE.NO AS?

OLAV AABREKK is the largest registered owner, with 100.0%.

What is the revenue of PRENTE.NO AS?

PRENTE.NO AS had revenue of NOK 60,000 in 2024.

Where is PRENTE.NO AS based?

PRENTE.NO AS has its business address in Sandane.

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.