biztrac. BETA
COMPANY REGISTER PROFILE
996526569 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Retail sale of household utensils, cutlery, crockery, glassware, tableware, china and pottery

SKARPEKNIVER AS

Org. no. 996526569 Limited company (AS) Oslo Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 33.8m
Operating profit NOK 6.8m
Equity NOK 13.0m
Incorporated 2010
Employees 9
Share capital NOK 157,000

SKARPEKNIVER AS is registered as a limited company in Oslo, Oslo with organisation number 996526569. The business is classified under retail sale of household utensils, cutlery, crockery, glassware, tableware, china and pottery (NACE 47.553). The company was incorporated in 2010 and has 9 registered employees. Registered share capital is NOK 157,000, divided into 1572 shares. The company's stated purpose is: “Import, distribusjon og salg av kjøkkenutstyr, -artikler og matvarer.”. The most recent filed accounts, for the 2025 financial year, show NOK 33.8m in revenue and NOK 6.8m in operating profit.

Key figures · 2025

Revenue
NOK 33.8m
▲ +70 %
Operating profit
NOK 6.8m
▲ +797 %
Equity
NOK 13.0m
▲ +58 %
Est. value
NOK 20.9m

Financial health · 2025

Liquidity
2.68
Very good
Current assets ÷ current liabilities
Profitability
43.6%
Very good
Return on total assets
Solidity
62.8%
Very good
Equity as a share of total capital

Who owns SKARPEKNIVER AS?

SKARPEKNIVER AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SKARPEKNIVER AS

Who owns SKARPEKNIVER AS?

VORBA AS is the largest registered owner, with 49.0%.

What is the revenue of SKARPEKNIVER AS?

SKARPEKNIVER AS had revenue of NOK 33.8m in 2025.

Who is the general manager of SKARPEKNIVER AS?

Alexander Waagaard Aagreen is registered as general manager of SKARPEKNIVER AS.

Where is SKARPEKNIVER AS based?

SKARPEKNIVER 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 03.10.2026.

Report a problem

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