BIZTRAC BETA
Restaurant activities

STYKKE PIPA AS

Org. no. 928462730 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 13.2m
Operating profit NOK 1.3m
Equity NOK 1.2m
Incorporated 2021
Employees 22
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

STYKKE PIPA AS is registered as a limited company in Oslo, Oslo with organisation number 928462730. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2021 and has 22 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Serveringsvirksomhet og annen virksomhet som står i forbindelse med dette samt deltagelse i andre selskaper med lignende formål. Investere i aksjer, utleie av personell, samt hva som hermed kan settes i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.2m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 13.2m
Operating profit
NOK 1.3m
Equity
NOK 1.2m
Est. value
NOK 5.3m

Financial health · 2024

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

Who owns STYKKE PIPA AS?

STYKKE AS
STYKKE PIPA AS
NOK 13.2m rev. · NOK 1.3m profit

STYKKE PIPA AS has 1 registered shareholder:

All shareholders and roles →

Group structure

STYKKE PIPA AS er morselskap for 1 datterselskap:

Frequently asked questions about STYKKE PIPA AS

Who owns STYKKE PIPA AS?

STYKKE AS is the largest registered owner, with 100.0%.

What is the revenue of STYKKE PIPA AS?

STYKKE PIPA AS had revenue of NOK 13.2m in 2024.

Where is STYKKE PIPA AS based?

STYKKE PIPA 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.