BIZTRAC BETA
Rental and operating of own or leased real estate

TVETER EIENDOM AS

Org. no. 892708142 Limited company (AS) Larvik Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 29,000
Operating profit NOK −62,000
Equity NOK 464,000
Incorporated 2008
Share capital NOK 30,000

Signals

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

TVETER EIENDOM AS is registered as a limited company in Larvik, Vestfold with organisation number 892708142. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utleie av fast eiendom og annet i den forbindelse, samt opplag og service på båter og motorer.”. The most recent filed accounts, for the 2025 financial year, show NOK 29,000 in revenue and NOK −62,000 in operating profit.

Key figures · 2025

Revenue
NOK 29,000
Operating profit
NOK −62,000
Equity
NOK 464,000
Est. value
NOK 345,000

Financial health · 2025

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

Who owns TVETER EIENDOM AS?

TVETER INVEST AS
TVETER EIENDOM AS
NOK 29,000 rev. · NOK −62,000 profit

TVETER EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TVETER EIENDOM AS own?

TVETER EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TVETER EIENDOM AS

Who owns TVETER EIENDOM AS?

TVETER INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of TVETER EIENDOM AS?

TVETER EIENDOM AS had revenue of NOK 29,000 in 2025.

Where is TVETER EIENDOM AS based?

TVETER EIENDOM AS has its business address in Larvik.

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.