BIZTRAC BETA
Retail sale of sports equipment

MYSEN DEKK OG KEBAB AS

Org. no. 923527168 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −2.2m
Equity NOK 3.5m
Incorporated 2019
Share capital NOK 60,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,2 mill kr).

MYSEN DEKK OG KEBAB AS is registered as a limited company in Oslo, Oslo with organisation number 923527168. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2019. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2024

Operating profit
NOK −2.2m
Equity
NOK 3.5m
Est. value
NOK 4.4m

Financial health · 2024

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

Who owns MYSEN DEKK OG KEBAB AS?

STEIN HENRIK HAUGEN
MYSEN DEKK OG KEBAB AS
· NOK −2.2m profit

MYSEN DEKK OG KEBAB AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MYSEN DEKK OG KEBAB AS own?

MYSEN DEKK OG KEBAB AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MYSEN DEKK OG KEBAB AS

Who owns MYSEN DEKK OG KEBAB AS?

STEIN HENRIK HAUGEN is the largest registered owner, with 100.0%.

Who is the general manager of MYSEN DEKK OG KEBAB AS?

Stein Henrik Haugen is registered as general manager of MYSEN DEKK OG KEBAB AS.

Where is MYSEN DEKK OG KEBAB AS based?

MYSEN DEKK OG KEBAB 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.