BIZTRAC BETA
General medical practice activities

SILKO AS

Org. no. 998751608 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK 1.5m
Equity NOK 313,000
Incorporated 2012
Share capital NOK 30,000

SILKO AS is registered as a limited company in Oslo, Oslo with organisation number 998751608. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Legetjenester. Medisinsk virksomhet. Konsulentvirksomhet. Handelsvirksomhet og andre tjenester som kjøp, salg av varer, import og eksport av varer og dertil hørende virksomhet. Investering i verdipapirer, virksomhet og eiendom samt øvrige virksomheter som faller naturlig under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK 1.5m
Equity
NOK 313,000
Est. value
NOK 5.1m

Financial health · 2024

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

Who owns SILKO AS?

OLAV KARSTAD
SILKO AS
NOK 2.5m rev. · NOK 1.5m profit

SILKO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SILKO AS own?

SILKO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SILKO AS

Who owns SILKO AS?

OLAV KARSTAD is the largest registered owner, with 100.0%.

What is the revenue of SILKO AS?

SILKO AS had revenue of NOK 2.5m in 2024.

Who is the general manager of SILKO AS?

Olav Karstad is registered as general manager of SILKO AS.

Where is SILKO AS based?

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