BIZTRAC BETA
Washing and cleaning of textile and fur products

AKERSHUS VASK AS

Org. no. 994288768 Limited company (AS) Oslo Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −39,000
Equity NOK 2.6m
Incorporated 2009
Share capital NOK 320,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−39k kr).

AKERSHUS VASK AS is registered as a limited company in Oslo, Oslo with organisation number 994288768. The business is classified under washing and cleaning of textile and fur products (NACE 96.100). The company was incorporated in 2009. Registered share capital is NOK 320,000, divided into 320 shares. The company's stated purpose is: “Vaskeritjenester og transporttjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −39,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −39,000
Equity
NOK 2.6m
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns AKERSHUS VASK AS?

OKTAY CELIK
AKERSHUS VASK AS
NOK 0 rev. · NOK −39,000 profit

AKERSHUS VASK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AKERSHUS VASK AS own?

AKERSHUS VASK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AKERSHUS VASK AS

Who owns AKERSHUS VASK AS?

OKTAY CELIK is the largest registered owner, with 100.0%.

What is the revenue of AKERSHUS VASK AS?

AKERSHUS VASK AS had revenue of NOK 0 in 2024.

Who is the general manager of AKERSHUS VASK AS?

Oktay Celik is registered as general manager of AKERSHUS VASK AS.

Where is AKERSHUS VASK AS based?

AKERSHUS VASK 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.