BIZTRAC BETA
COMPANY REGISTER PROFILE
936794238 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

EKT VEKST AS

Org. no. 936794238 Limited company (AS) Stavanger Incorporated 2025 Active
Ownership graph ↗
Equity NOK 4.3m
Incorporated 2025
Share capital NOK 35,000

EKT VEKST AS is registered as a limited company in Stavanger, Rogaland with organisation number 936794238. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 35,000, divided into 30000 shares. The company's stated purpose is: “Erverve, eie og forvalte aksjer og andeler i andre selskaper og alt som naturlig hører inn under dette.”.

Former names: ELISABETH KVAMME TOKVAM INVEST AS

Key figures · 2025

Equity
NOK 4.3m
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns EKT VEKST AS?

EKT VEKST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EKT VEKST AS own?

EKT VEKST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EKT VEKST AS

Who owns EKT VEKST AS?

ELISABETH KVAMME TOKVAM is the largest registered owner, with 100.0%.

Where is EKT VEKST AS based?

EKT VEKST AS has its business address in Hafrsfjord.

Property

Business address Fasanveien 45B, 4042 Hafrsfjord
Cadastral unit 1103-38/3900/0/0
Building Enebolig m/hybel/sokkelleil. · 2 units

2 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.