BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

ALLEEN KIOSK AS

Org. no. 997543017 Limited company (AS) Lyngdal Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 17.1m
Operating profit NOK 1.4m
Equity NOK 1.7m
Incorporated 2011
Employees 15
Share capital NOK 102,000

ALLEEN KIOSK AS is registered as a limited company in Lyngdal, Agder with organisation number 997543017. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2011 and has 15 registered employees. Registered share capital is NOK 102,000, divided into 102 shares. The company's stated purpose is: “Kioskhandel med bredt vareutvalg med hovedvekt på nærings- og nytelsesmidler og hva dermed står i sammenheng, investering i aksjer og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 17.1m in revenue and NOK 1.4m in operating profit.

Key figures · 2025

Revenue
NOK 17.1m
Operating profit
NOK 1.4m
Equity
NOK 1.7m
Est. value
NOK 5.6m

Financial health · 2025

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

Who owns ALLEEN KIOSK AS?

SISSEL SVINDLAND
ALLEEN KIOSK AS
NOK 17.1m rev. · NOK 1.4m profit

ALLEEN KIOSK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ALLEEN KIOSK AS

Who owns ALLEEN KIOSK AS?

SISSEL SVINDLAND is the largest registered owner, with 50.0%.

What is the revenue of ALLEEN KIOSK AS?

ALLEEN KIOSK AS had revenue of NOK 17.1m in 2025.

Who is the general manager of ALLEEN KIOSK AS?

Sissel Svindland is registered as general manager of ALLEEN KIOSK AS.

Where is ALLEEN KIOSK AS based?

ALLEEN KIOSK AS has its business address in Lyngdal.

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.