BIZTRAC BETA
Event catering activities

SKRENTEN PIZZA AS

Org. no. 924328533 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 5.0m
Operating profit NOK −49,000
Equity NOK 238,000
Incorporated 2019
Employees 9
Share capital NOK 32,000

Signals

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

SKRENTEN PIZZA AS is registered as a limited company in Oslo, Oslo with organisation number 924328533. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 2019 and has 9 registered employees. Registered share capital is NOK 32,000, divided into 32 shares. The company's stated purpose is: “Selge og importere matvarer, samt det som naturlig står i forbindelse med dette, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.0m in revenue and NOK −49,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.0m
Operating profit
NOK −49,000
Equity
NOK 238,000
Est. value
NOK 3.6m

Financial health · 2025

Liquidity
1.19
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.2%
Good
Equity as a share of total capital

Who owns SKRENTEN PIZZA AS?

CAPTAINS ENTERPRISE AS
SKRENTEN PIZZA AS
NOK 5.0m rev. · NOK −49,000 profit

SKRENTEN PIZZA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKRENTEN PIZZA AS

Who owns SKRENTEN PIZZA AS?

CAPTAINS ENTERPRISE AS is the largest registered owner, with 100.0%.

What is the revenue of SKRENTEN PIZZA AS?

SKRENTEN PIZZA AS had revenue of NOK 5.0m in 2025.

Who is the general manager of SKRENTEN PIZZA AS?

Arne Christian Skagen is registered as general manager of SKRENTEN PIZZA AS.

Where is SKRENTEN PIZZA AS based?

SKRENTEN PIZZA 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.