BIZTRAC BETA
Other captive investment companies

LEITE INVEST AS

Org. no. 989216880 Limited company (AS) Kvinnherad Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 9.7m
Operating profit NOK 9.6m
Equity NOK 51.0m
Incorporated 2005
Share capital NOK 100,000

LEITE INVEST AS is registered as a limited company in Kvinnherad, Vestland with organisation number 989216880. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, videreutvikling, utleie og salg av fast eiendom og annen virksomhet som naturlig hører sammen med dette samt investering i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.7m in revenue and NOK 9.6m in operating profit.

Key figures · 2024

Revenue
NOK 9.7m
Operating profit
NOK 9.6m
Equity
NOK 51.0m
Est. value
NOK 57.2m

Financial health · 2025

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

Who owns LEITE INVEST AS?

HANS HELGE VIK
LEITE INVEST AS
NOK 9.7m rev. · NOK 9.6m profit

LEITE INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LEITE INVEST AS own?

LEITE INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about LEITE INVEST AS

Who owns LEITE INVEST AS?

HANS HELGE VIK is the largest registered owner, with 100.0%.

What is the revenue of LEITE INVEST AS?

LEITE INVEST AS had revenue of NOK 9.7m in 2024.

Who is the general manager of LEITE INVEST AS?

Hans Helge Vik is registered as general manager of LEITE INVEST AS.

Where is LEITE INVEST AS based?

LEITE INVEST AS has its business address in Fjelberg.

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.