BIZTRAC BETA
Other real estate activities on a fee or contract basis

VINJE SAG OG HØVLERI AS

Org. no. 911864959 Limited company (AS) Vinje Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK 495,000
Equity NOK 5.1m
Incorporated 2013
Share capital NOK 140,000

VINJE SAG OG HØVLERI AS is registered as a limited company in Vinje, Telemark with organisation number 911864959. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2013. Registered share capital is NOK 140,000, divided into 140 shares. The company's stated purpose is: “Verksemd med eigedomsforvaltning og det som naturleg høyrer til slik verksemd under dette og deltaka i andre selskap med liknande verksemd.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK 495,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK 495,000
Equity
NOK 5.1m
Est. value
NOK 5.0m

Financial health · 2024

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

Who owns VINJE SAG OG HØVLERI AS?

TJØNN AS
VINJE SAG OG HØVLERI AS
NOK 1.3m rev. · NOK 495,000 profit

VINJE SAG OG HØVLERI AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VINJE SAG OG HØVLERI AS

Who owns VINJE SAG OG HØVLERI AS?

TJØNN AS is the largest registered owner, with 50.0%.

What is the revenue of VINJE SAG OG HØVLERI AS?

VINJE SAG OG HØVLERI AS had revenue of NOK 1.3m in 2024.

Who is the general manager of VINJE SAG OG HØVLERI AS?

Tor Tjønn is registered as general manager of VINJE SAG OG HØVLERI AS.

Where is VINJE SAG OG HØVLERI AS based?

VINJE SAG OG HØVLERI AS has its business address in Vinje.

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.