biztrac. BETA
COMPANY REGISTER PROFILE
932605449 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Retail sale of pharmaceutical products

SYLVROKKEN AS

Org. no. 932605449 Limited company (AS) Ringebu Incorporated 2023 Active
Revenue 2025 NOK 0
Operating profit NOK −26,000
Equity NOK −9,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−9k kr).

SYLVROKKEN AS is registered as a limited company in Ringebu, Innlandet with organisation number 932605449. The business is classified under retail sale of pharmaceutical products (NACE 47.730). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Farmasøytiske tjenester, apotekdrift, rådgiving, freelanceoppdrag og investering.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −26,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −26,000
▼ −265 %
Equity
NOK −9,000
▼ −147 %

Financial health · 2025

Liquidity
19.32
Very good
Current assets ÷ current liabilities
Profitability
-23.0%
Not satisfactory
Return on total assets
Solidity
-4.5%
Weak
Equity as a share of total capital

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

Who owns SYLVROKKEN AS?

SYLVROKKEN AS
NOK 0 rev. · NOK −26,000 profit

SYLVROKKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SYLVROKKEN AS

Who owns SYLVROKKEN AS?

Skjalg Bruheim is the largest registered owner, with 100.0%.

What is the revenue of SYLVROKKEN AS?

SYLVROKKEN AS had revenue of NOK 0 in 2025.

Who is the general manager of SYLVROKKEN AS?

Skjalg Bruheim is registered as general manager of SYLVROKKEN AS.

Where is SYLVROKKEN AS based?

SYLVROKKEN AS has its business address in Ringebu.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.