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

KUBEN KOLONIAL AS

Org. no. 928070670 Limited company (AS) Lillehammer Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 21.4m
Operating profit NOK 1.6m
Equity NOK 100,000
Incorporated 2021
Employees 9
Share capital NOK 100,000

KUBEN KOLONIAL AS is registered as a limited company in Lillehammer, Innlandet with organisation number 928070670. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2021 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Dagligvarehandel med bredt vareutvalg med hovedvekt på nærings- og nytelsesmidler.”. The most recent filed accounts, for the 2024 financial year, show NOK 21.4m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 21.4m
Operating profit
NOK 1.6m
Equity
NOK 100,000
Est. value
NOK 5.8m

Financial health · 2024

Liquidity
0.90
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.2%
Not satisfactory
Equity as a share of total capital

Who owns KUBEN KOLONIAL AS?

MJØSA DRIFT AS
KUBEN KOLONIAL AS
NOK 21.4m rev. · NOK 1.6m profit

KUBEN KOLONIAL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KUBEN KOLONIAL AS

Who owns KUBEN KOLONIAL AS?

MJØSA DRIFT AS is the largest registered owner, with 100.0%.

What is the revenue of KUBEN KOLONIAL AS?

KUBEN KOLONIAL AS had revenue of NOK 21.4m in 2024.

Who is the general manager of KUBEN KOLONIAL AS?

Jørn Harald Villumstad Granum is registered as general manager of KUBEN KOLONIAL AS.

Where is KUBEN KOLONIAL AS based?

KUBEN KOLONIAL AS has its business address in Lillehammer.

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.