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

SKIBOTN VARESENTER AS

Org. no. 936706711 Limited company (AS) Storfjord Incorporated 1985 Active
Ownership graph ↗
Revenue 2025 NOK 23.5m
Operating profit NOK 1.1m
Equity NOK 9.1m
Incorporated 1985
Employees 12
Share capital NOK 100,000

SKIBOTN VARESENTER AS is registered as a limited company in Storfjord, Troms with organisation number 936706711. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 1985 and has 12 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Drive handel, samt deltakelse i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 23.5m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 23.5m
Operating profit
NOK 1.1m
Equity
NOK 9.1m
Est. value
NOK 9.9m

Financial health · 2025

Liquidity
4.36
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
79.5%
Very good
Equity as a share of total capital

Who owns SKIBOTN VARESENTER AS?

ROALD COUCHERON VARVIK
SKIBOTN VARESENTER AS
NOK 23.5m rev. · NOK 1.1m profit

SKIBOTN VARESENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKIBOTN VARESENTER AS

Who owns SKIBOTN VARESENTER AS?

ROALD COUCHERON VARVIK is the largest registered owner, with 100.0%.

What is the revenue of SKIBOTN VARESENTER AS?

SKIBOTN VARESENTER AS had revenue of NOK 23.5m in 2025.

Who is the general manager of SKIBOTN VARESENTER AS?

Roald Coucheron Varvik is registered as general manager of SKIBOTN VARESENTER AS.

Where is SKIBOTN VARESENTER AS based?

SKIBOTN VARESENTER AS has its business address in Skibotn.

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.