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

OLES KOLONIAL AS

Org. no. 914320089 Limited company (AS) Lebesby Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 24.1m
Operating profit NOK 282,000
Equity NOK 1.4m
Incorporated 2014
Employees 12
Share capital NOK 73,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

OLES KOLONIAL AS is registered as a limited company in Lebesby, Finnmark with organisation number 914320089. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2014 and has 12 registered employees. Registered share capital is NOK 73,000, divided into 300 shares. The company's stated purpose is: “Varehandel med dertil hørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 24.1m in revenue and NOK 282,000 in operating profit.

Key figures · 2024

Revenue
NOK 24.1m
Operating profit
NOK 282,000
Equity
NOK 1.4m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns OLES KOLONIAL AS?

OML AS
OLES KOLONIAL AS
NOK 24.1m rev. · NOK 282,000 profit

OLES KOLONIAL AS has 1 registered shareholder:

All shareholders and roles →

Group structure

OLES KOLONIAL AS er morselskap for 2 datterselskaper:

Frequently asked questions about OLES KOLONIAL AS

Who owns OLES KOLONIAL AS?

OML AS is the largest registered owner, with 100.0%.

What is the revenue of OLES KOLONIAL AS?

OLES KOLONIAL AS had revenue of NOK 24.1m in 2024.

Where is OLES KOLONIAL AS based?

OLES KOLONIAL AS has its business address in Kjøllefjord.

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.