BIZTRAC BETA
COMPANY REGISTER PROFILE
937371381 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Other real estate activities on a fee or contract basis

VIKSE CAPITAL AS

Org. no. 937371381 Limited company (AS) Tønsberg Incorporated 2026 Active
Ownership graph ↗
Incorporated 2026
Share capital NOK 50,000

Signals

2 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2026-02-28.

VIKSE CAPITAL AS is registered as a limited company in Tønsberg, Vestfold with organisation number 937371381. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2026. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Selge varer og tjenester innen eiendomsforvaltning, og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”.

Former names: TERRA CAPITAL ADVISORY AS

Who owns VIKSE CAPITAL AS?

No shareholders are registered for VIKSE CAPITAL AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about VIKSE CAPITAL AS

Who is the general manager of VIKSE CAPITAL AS?

Paul Thorstein Vikse is registered as general manager of VIKSE CAPITAL AS.

Where is VIKSE CAPITAL AS based?

VIKSE CAPITAL AS has its business address in Tønsberg.

Property

Business address Storgaten 32, 3126 Tønsberg
Cadastral unit 3905-1002/266/0/0
Building Kjøpesenter, varehus · 57 units

123 companies are registered at this address.

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.