BIZTRAC BETA
Business and other management consultancy activities

PAJA AS

Org. no. 927385899 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 886,000
Operating profit NOK 730,000
Equity NOK 1.4m
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-04-20 Aksjekapital registrert 2026-04-20.

PAJA AS is registered as a limited company in Oslo, Oslo with organisation number 927385899. 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: “Eie aksjer og andeler i andre selskaper. Selskapet kan også investere i fast eiendom samt leie ut personell.”. The most recent filed accounts, for the 2025 financial year, show NOK 886,000 in revenue and NOK 730,000 in operating profit.

Key figures · 2025

Revenue
NOK 886,000
Operating profit
NOK 730,000
Equity
NOK 1.4m
Est. value
NOK 3.2m

Financial health · 2025

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

Who owns PAJA AS?

PAAL VEGARD JAHRMANN
PAJA AS
NOK 886,000 rev. · NOK 730,000 profit

PAJA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PAJA AS own?

PAJA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PAJA AS

Who owns PAJA AS?

PAAL VEGARD JAHRMANN is the largest registered owner, with 100.0%.

What is the revenue of PAJA AS?

PAJA AS had revenue of NOK 886,000 in 2025.

Who is the general manager of PAJA AS?

Paal Vegard Jahrmann is registered as general manager of PAJA AS.

Where is PAJA AS based?

PAJA 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.