biztrac. BETA
COMPANY REGISTER PROFILE
927467356 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

FLEXCAP AS

Org. no. 927467356 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK 1.8m
Incorporated 2021
Share capital NOK 2.0m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2k kr).
  • Nylig endring 2026-07-14 Adresseendring registrert 2026-07-14.

FLEXCAP AS is registered as a limited company in Bergen, Vestland with organisation number 927467356. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 2.0m, divided into 2000000 shares. The company's stated purpose is: “Å investere i aksjer og andre verdipapirer og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
▲ +66 %
Equity
NOK 1.8m
▲ +63 %
Est. value
NOK 5.7m

Financial health · 2025

Liquidity
1.58
Good
Current assets ÷ current liabilities
Profitability
36.1%
Very good
Return on total assets
Solidity
89.2%
Very good
Equity as a share of total capital

Who owns FLEXCAP AS?

FLEXCAP AS
NOK 0 rev. · NOK −2,000 profit

FLEXCAP AS has 2 registered shareholders:

All shareholders and roles →

Which companies does FLEXCAP AS own?

FLEXCAP AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FLEXCAP AS

Who owns FLEXCAP AS?

Kenneth Bagameri is the largest registered owner, with 50.0%.

What is the revenue of FLEXCAP AS?

FLEXCAP AS had revenue of NOK 0 in 2025.

Where is FLEXCAP AS based?

FLEXCAP AS has its business address in Søreidgrend.

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.