BIZTRAC BETA
COMPANY REGISTER PROFILE
936492274 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

TVEIT CAPITAL AS

Org. no. 936492274 Limited company (AS) Bergen Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2025-10-11.

TVEIT CAPITAL AS is registered as a limited company in Bergen, Vestland with organisation number 936492274. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Who owns TVEIT CAPITAL AS?

TVEIT CAPITAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TVEIT CAPITAL AS own?

TVEIT CAPITAL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TVEIT CAPITAL AS

Who owns TVEIT CAPITAL AS?

Arve Aron Tveit is the largest registered owner, with 100.0%.

Who is the general manager of TVEIT CAPITAL AS?

Arve Aron Tveit is registered as general manager of TVEIT CAPITAL AS.

Where is TVEIT CAPITAL AS based?

TVEIT CAPITAL AS has its business address in Bergen.

Property

Business address Grønnlien 14C, 5055 Bergen
Cadastral unit 4601-159/939/0/0
Building Rekkehus · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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