BIZTRAC BETA
Business and other management consultancy activities

PAVI AS

Org. no. 926505882 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −22,000
Equity NOK 173,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−22k kr).

PAVI AS is registered as a limited company in Oslo, Oslo with organisation number 926505882. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selskapet skal selge tjenester og varer innen prosjektering, rådgivning, utvikling, IT, transport, bygg, håndverksarbeid - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −22,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK −22,000
Equity
NOK 173,000
Est. value
NOK 982,000

Financial health · 2025

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

Who owns PAVI AS?

KRISTIAN VIKENES
PAVI AS
NOK 1.1m rev. · NOK −22,000 profit

PAVI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PAVI AS

Who owns PAVI AS?

KRISTIAN VIKENES is the largest registered owner, with 100.0%.

What is the revenue of PAVI AS?

PAVI AS had revenue of NOK 1.1m in 2025.

Who is the general manager of PAVI AS?

Kristian Vikenes is registered as general manager of PAVI AS.

Where is PAVI AS based?

PAVI AS has its business address in Oslo.

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.