biztrac. BETA
COMPANY REGISTER PROFILE
934632389 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

POJOSOK AS

Org. no. 934632389 Limited company (AS) Bergen Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −17,000
Equity NOK 10.7m
Incorporated 2024
Share capital NOK 110,000

Signals

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

POJOSOK AS is registered as a limited company in Bergen, Vestland with organisation number 934632389. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 110,000, divided into 109920 shares. The company's stated purpose is: “Investere i selskaper og fast eiendom og forvaltning av slike, samt det som er naturlig står i forbindelse med dette. Selskapet skal kunne delta i andre foretak, herunder investering i aksjer, aksjefond o.l.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −17,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −17,000
▼ −192 %
Equity
NOK 10.7m
▲ +3 %
Est. value
NOK 7.9m

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
3.3%
Weak
Return on total assets
Solidity
97.6%
Very good
Equity as a share of total capital

Who owns POJOSOK AS?

POJOSOK AS
NOK 0 rev. · NOK −17,000 profit

POJOSOK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does POJOSOK AS own?

POJOSOK AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about POJOSOK AS

Who owns POJOSOK AS?

Per Ole Jøsok is the largest registered owner, with 100.0%.

What is the revenue of POJOSOK AS?

POJOSOK AS had revenue of NOK 0 in 2025.

Where is POJOSOK AS based?

POJOSOK AS has its business address in Søreidgrend.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.