BIZTRAC BETA
Hairdressing and barber activities

SYVOGTYVE AS

Org. no. 913928342 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 8.4m
Operating profit NOK 211,000
Equity NOK 1.4m
Incorporated 2014
Employees 7
Share capital NOK 30,000

SYVOGTYVE AS is registered as a limited company in Oslo, Oslo with organisation number 913928342. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2014 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive frisørvirksomhet samt alt som står i forbindelse hermed, deltakelse i andre selskap med lignende virksomhet, samt kursvirksomt for frisørbransjen.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.4m in revenue and NOK 211,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.4m
Operating profit
NOK 211,000
Equity
NOK 1.4m
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns SYVOGTYVE AS?

JØRGEN LILLELØKKEN
SYVOGTYVE AS
NOK 8.4m rev. · NOK 211,000 profit

SYVOGTYVE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SYVOGTYVE AS own?

SYVOGTYVE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SYVOGTYVE AS

Who owns SYVOGTYVE AS?

JØRGEN LILLELØKKEN is the largest registered owner, with 100.0%.

What is the revenue of SYVOGTYVE AS?

SYVOGTYVE AS had revenue of NOK 8.4m in 2024.

Who is the general manager of SYVOGTYVE AS?

Jørgen Lilleløkken is registered as general manager of SYVOGTYVE AS.

Where is SYVOGTYVE AS based?

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