BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

PRETO AS

Org. no. 988978744 Limited company (AS) Alver Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 174,000
Operating profit NOK 5,000
Equity NOK 38.9m
Incorporated 2005
Share capital NOK 100,000

PRETO AS is registered as a limited company in Alver, Vestland with organisation number 988978744. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 456 shares. The company's stated purpose is: “Investering i andre selskap og eiendom, samt hva derved står i sammenheng. Selskapet skal også kunne forestå administrative tjenester for andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 174,000 in revenue and NOK 5,000 in operating profit.

Key figures · 2024

Revenue
NOK 174,000
Operating profit
NOK 5,000
Equity
NOK 38.9m
Est. value
NOK 24.4m

Financial health · 2024

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

Who owns PRETO AS?

TONE OLSVOLL EIDE
PRETO AS
NOK 174,000 rev. · NOK 5,000 profit

PRETO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PRETO AS own?

PRETO AS holds stakes in 9 companies:

See the full ownership structure →

Frequently asked questions about PRETO AS

Who owns PRETO AS?

TONE OLSVOLL EIDE is the largest registered owner, with 100.0%.

What is the revenue of PRETO AS?

PRETO AS had revenue of NOK 174,000 in 2024.

Who is the general manager of PRETO AS?

Tone Olsvoll Eide is registered as general manager of PRETO AS.

Where is PRETO AS based?

PRETO AS has its business address in Alversund.

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.