biztrac. BETA
COMPANY REGISTER PROFILE
916008589 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

TVEITAN HOLDING AS

Org. no. 916008589 Limited company (AS) Midt-Telemark Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK 19.7m
Incorporated 2015
Share capital NOK 130,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TVEITAN HOLDING AS is registered as a limited company in Midt-Telemark, Telemark with organisation number 916008589. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 130,000, divided into 100 shares. The company's stated purpose is: “Å eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytning til dette.”.

Key figures · 2025

Operating profit
NOK −7,000
▲ +60 %
Equity
NOK 19.7m
▲ +3 %
Est. value
NOK 15.4m

Financial health · 2025

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

Who owns TVEITAN HOLDING AS?

TVEITAN HOLDING AS
· NOK −7,000 profit

TVEITAN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TVEITAN HOLDING AS own?

TVEITAN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TVEITAN HOLDING AS

Who owns TVEITAN HOLDING AS?

Mona Tveitan is the largest registered owner, with 100.0%.

Where is TVEITAN HOLDING AS based?

TVEITAN HOLDING AS has its business address in Bø I Telemark.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.