BIZTRAC BETA
Other information technology and computer service activities

FLEXI VEKST AS

Org. no. 927760142 Limited company (AS) Sandnes Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −12,000
Equity NOK 17.0m
Incorporated 2021
Share capital NOK 180,000

Signals

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

FLEXI VEKST AS is registered as a limited company in Sandnes, Rogaland with organisation number 927760142. The business is classified under other information technology and computer service activities (NACE 62.900). The company was incorporated in 2021. Registered share capital is NOK 180,000, divided into 80000 shares. The company's stated purpose is: “Eie, selge og kjøpe aksjer og eiendom og alt hva det måtte innebære.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 17.0m
Est. value
NOK 42.3m

Financial health · 2025

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

Who owns FLEXI VEKST AS?

ARILD SVELA
FLEXI VEKST AS
NOK 0 rev. · NOK −12,000 profit

FLEXI VEKST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FLEXI VEKST AS own?

FLEXI VEKST AS holds a stake in 1 company:

See the full ownership structure →

Group structure

FLEXI VEKST AS er morselskap for 1 datterselskap:

Frequently asked questions about FLEXI VEKST AS

Who owns FLEXI VEKST AS?

ARILD SVELA is the largest registered owner, with 100.0%.

What is the revenue of FLEXI VEKST AS?

FLEXI VEKST AS had revenue of NOK 0 in 2025.

Where is FLEXI VEKST AS based?

FLEXI VEKST AS has its business address in Sandnes.

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.