BIZTRAC BETA
Retail sale of sports equipment

VEST-TELEMARK VÅPEN OG VILLMARK AS

Org. no. 929062639 Limited company (AS) Vinje Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 349,000
Equity NOK 584,000
Incorporated 2022
Share capital NOK 30,000

VEST-TELEMARK VÅPEN OG VILLMARK AS is registered as a limited company in Vinje, Telemark with organisation number 929062639. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Børsemakertenester, salg av våpen, ammunisjon, rekvisita, sportsutstyr og det som naturleg høyer inn under det. Sal av tenester inkludert mekanisk arbeid og utleige av personell.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 349,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK 349,000
Equity
NOK 584,000
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns VEST-TELEMARK VÅPEN OG VILLMARK AS?

KNUT NYLEND
VEST-TELEMARK VÅPEN OG VILLMARK AS
NOK 2.1m rev. · NOK 349,000 profit

VEST-TELEMARK VÅPEN OG VILLMARK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VEST-TELEMARK VÅPEN OG VILLMARK AS

Who owns VEST-TELEMARK VÅPEN OG VILLMARK AS?

KNUT NYLEND is the largest registered owner, with 100.0%.

What is the revenue of VEST-TELEMARK VÅPEN OG VILLMARK AS?

VEST-TELEMARK VÅPEN OG VILLMARK AS had revenue of NOK 2.1m in 2025.

Where is VEST-TELEMARK VÅPEN OG VILLMARK AS based?

VEST-TELEMARK VÅPEN OG VILLMARK AS has its business address in Rauland.

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.