BIZTRAC BETA
Business and other management consultancy activities

KOSTVEIT HOLDING AS

Org. no. 931099191 Limited company (AS) Vinje Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 17,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).

KOSTVEIT HOLDING AS is registered as a limited company in Vinje, Telemark with organisation number 931099191. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Å investere og forvalte investeringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 17,000
Est. value
NOK 28,000

Financial health · 2025

Liquidity
0.07
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KOSTVEIT HOLDING AS?

TROND KOSTVEIT
KOSTVEIT HOLDING AS
NOK 0 rev. · NOK −5,000 profit

KOSTVEIT HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KOSTVEIT HOLDING AS own?

KOSTVEIT HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KOSTVEIT HOLDING AS

Who owns KOSTVEIT HOLDING AS?

TROND KOSTVEIT is the largest registered owner, with 100.0%.

What is the revenue of KOSTVEIT HOLDING AS?

KOSTVEIT HOLDING AS had revenue of NOK 0 in 2025.

Where is KOSTVEIT HOLDING AS based?

KOSTVEIT HOLDING 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.