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

KNUT BYE KOLONIAL AS

Org. no. 923085009 Limited company (AS) Vardø Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 37.5m
Operating profit NOK 850,000
Equity NOK 2.3m
Incorporated 2019
Employees 17
Share capital NOK 100,000

KNUT BYE KOLONIAL AS is registered as a limited company in Vardø, Finnmark with organisation number 923085009. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2019 and has 17 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive med dagligvarehandel samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 37.5m in revenue and NOK 850,000 in operating profit.

Key figures · 2024

Revenue
NOK 37.5m
Operating profit
NOK 850,000
Equity
NOK 2.3m
Est. value
NOK 3.8m

Financial health · 2024

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

Who owns KNUT BYE KOLONIAL AS?

TRMLF HOLDING AS
KNUT BYE KOLONIAL AS
NOK 37.5m rev. · NOK 850,000 profit

KNUT BYE KOLONIAL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KNUT BYE KOLONIAL AS

Who owns KNUT BYE KOLONIAL AS?

TRMLF HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KNUT BYE KOLONIAL AS?

KNUT BYE KOLONIAL AS had revenue of NOK 37.5m in 2024.

Who is the general manager of KNUT BYE KOLONIAL AS?

Tom Rainer Mikalsen Fjelde is registered as general manager of KNUT BYE KOLONIAL AS.

Where is KNUT BYE KOLONIAL AS based?

KNUT BYE KOLONIAL AS has its business address in Vardø.

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.