BIZTRAC BETA
Business and other management consultancy activities

PIRI AS

Org. no. 988809608 Limited company (AS) Sandnes Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 27,000
Operating profit NOK 3,000
Equity NOK −134,000
Incorporated 2005
Share capital NOK 150,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−134k kr).

PIRI AS is registered as a limited company in Sandnes, Rogaland with organisation number 988809608. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2005. Registered share capital is NOK 150,000, divided into 1500 shares. The company's stated purpose is: “Investering i andre selskaper samt konsulenttjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 27,000 in revenue and NOK 3,000 in operating profit.

Key figures · 2025

Revenue
NOK 27,000
Operating profit
NOK 3,000
Equity
NOK −134,000
Est. value
NOK 13,000

Financial health · 2025

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

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

Who owns PIRI AS?

ODD MAGNE VATNE
PIRI AS
NOK 27,000 rev. · NOK 3,000 profit

PIRI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PIRI AS own?

PIRI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PIRI AS

Who owns PIRI AS?

ODD MAGNE VATNE is the largest registered owner, with 100.0%.

What is the revenue of PIRI AS?

PIRI AS had revenue of NOK 27,000 in 2025.

Who is the general manager of PIRI AS?

Odd Magne Vatne is registered as general manager of PIRI AS.

Where is PIRI AS based?

PIRI AS has its business address in Sandnes.

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.