BIZTRAC BETA
Restaurant activities

STYKKE U2 AS

Org. no. 933350223 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −35,000
Equity NOK −5,000
Incorporated 2024
Employees 20
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−5k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−35k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

STYKKE U2 AS is registered as a limited company in Oslo, Oslo with organisation number 933350223. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2024 and has 20 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.”.

Key figures · 2024

Operating profit
NOK −35,000
Equity
NOK −5,000

Financial health · 2024

Liquidity
0.06
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns STYKKE U2 AS?

STYKKE AS
STYKKE U2 AS
· NOK −35,000 profit

STYKKE U2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STYKKE U2 AS

Who owns STYKKE U2 AS?

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

Who is the general manager of STYKKE U2 AS?

Anders Holmefjord Lillevik is registered as general manager of STYKKE U2 AS.

Where is STYKKE U2 AS based?

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