BIZTRAC BETA
Repair and maintenance of footwear and leather goods

SANA SKO OG NØKKELSERVICE AS

Org. no. 899330102 Limited company (AS) Asker Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 28,000
Equity NOK 386,000
Incorporated 2012
Share capital NOK 30,000

SANA SKO OG NØKKELSERVICE AS is registered as a limited company in Asker, Akershus with organisation number 899330102. The business is classified under repair and maintenance of footwear and leather goods (NACE 95.230). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Reparasjon av skotøy og lærvarer, samt filing av nøkler og salg av varer.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 28,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 28,000
Equity
NOK 386,000
Est. value
NOK 344,000

Financial health · 2025

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

Who owns SANA SKO OG NØKKELSERVICE AS?

SAMI IBRAHIM
SANA SKO OG NØKKELSERVICE AS
NOK 1.6m rev. · NOK 28,000 profit

SANA SKO OG NØKKELSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SANA SKO OG NØKKELSERVICE AS

Who owns SANA SKO OG NØKKELSERVICE AS?

SAMI IBRAHIM is the largest registered owner, with 100.0%.

What is the revenue of SANA SKO OG NØKKELSERVICE AS?

SANA SKO OG NØKKELSERVICE AS had revenue of NOK 1.6m in 2025.

Who is the general manager of SANA SKO OG NØKKELSERVICE AS?

Sami Ibrahim is registered as general manager of SANA SKO OG NØKKELSERVICE AS.

Where is SANA SKO OG NØKKELSERVICE AS based?

SANA SKO OG NØKKELSERVICE AS has its business address in Asker.

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.