BIZTRAC BETA
Uoppgitt

KIOSKEN HOLDING AS

Org. no. 931691791 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 43,000
Equity NOK 99,000
Incorporated 2023
Share capital NOK 30,000

KIOSKEN HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 931691791. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i andre selskaper og annen økonomisk virksomhet som naturlig ligger inn under dette, herunder eie aksjer og andeler i annen virksomhet, investeringer i aksjefond og andre verdipapirer, samt øvrig investeringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 43,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 43,000
Equity
NOK 99,000
Est. value
NOK 216,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KIOSKEN HOLDING AS?

ANINE ECKHOFF ISING
KIOSKEN HOLDING AS
NOK 1.2m rev. · NOK 43,000 profit

KIOSKEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KIOSKEN HOLDING AS

Who owns KIOSKEN HOLDING AS?

ANINE ECKHOFF ISING is the largest registered owner, with 100.0%.

What is the revenue of KIOSKEN HOLDING AS?

KIOSKEN HOLDING AS had revenue of NOK 1.2m in 2024.

Who is the general manager of KIOSKEN HOLDING AS?

Anine Eckhoff Ising is registered as general manager of KIOSKEN HOLDING AS.

Where is KIOSKEN HOLDING AS based?

KIOSKEN HOLDING 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.