BIZTRAC BETA
Rental and operating of own or leased real estate

FINDERENG HYTTEFERIE AS

Org. no. 881405032 Limited company (AS) Kviteseid Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 842,000
Operating profit NOK 308,000
Equity NOK 472,000
Incorporated 1999
Share capital NOK 400,000

FINDERENG HYTTEFERIE AS is registered as a limited company in Kviteseid, Telemark with organisation number 881405032. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1999. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Eige og drive utleigehytter og det som naturleg høyrer til slik verksemd.”. The most recent filed accounts, for the 2024 financial year, show NOK 842,000 in revenue and NOK 308,000 in operating profit.

Key figures · 2024

Revenue
NOK 842,000
Operating profit
NOK 308,000
Equity
NOK 472,000
Est. value
NOK 1.1m

Financial health · 2024

Liquidity
0.79
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.2%
Good
Equity as a share of total capital

Who owns FINDERENG HYTTEFERIE AS?

TOR OLAV VELLENE TVEIT
FINDERENG HYTTEFERIE AS
NOK 842,000 rev. · NOK 308,000 profit

FINDERENG HYTTEFERIE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FINDERENG HYTTEFERIE AS

Who owns FINDERENG HYTTEFERIE AS?

TOR OLAV VELLENE TVEIT is the largest registered owner, with 70.0%.

What is the revenue of FINDERENG HYTTEFERIE AS?

FINDERENG HYTTEFERIE AS had revenue of NOK 842,000 in 2024.

Who is the general manager of FINDERENG HYTTEFERIE AS?

Marit Johanne Folkestadås Tveit is registered as general manager of FINDERENG HYTTEFERIE AS.

Where is FINDERENG HYTTEFERIE AS based?

FINDERENG HYTTEFERIE AS has its business address in Vrådal.

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.