BIZTRAC BETA
Restaurant activities

PILLEFYKEN AS

Org. no. 923957596 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −158,000
Equity NOK −181,000
Incorporated 2019
Employees 5
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−181k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−158k kr).

PILLEFYKEN AS is registered as a limited company in Oslo, Oslo with organisation number 923957596. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2019 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drift av restaurant, kafe virksomhet og konsultasjon innen samme bransje.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −158,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK −158,000
Equity
NOK −181,000

Financial health · 2025

Liquidity
24.10
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-7.0%
Weak
Equity as a share of total capital

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

Who owns PILLEFYKEN AS?

SKYTTEL HOLDING AS
PILLEFYKEN AS
NOK 1.1m rev. · NOK −158,000 profit

PILLEFYKEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PILLEFYKEN AS

Who owns PILLEFYKEN AS?

SKYTTEL HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of PILLEFYKEN AS?

PILLEFYKEN AS had revenue of NOK 1.1m in 2025.

Who is the general manager of PILLEFYKEN AS?

Susanne Martens Låstad is registered as general manager of PILLEFYKEN AS.

Where is PILLEFYKEN AS based?

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