BIZTRAC BETA
Rental and operating of own or leased real estate

FLEXI HOLDING AS

Org. no. 916196121 Limited company (AS) Skien Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 200,000
Operating profit NOK 161,000
Equity NOK 723,000
Incorporated 2015
Share capital NOK 30,000

FLEXI HOLDING AS is registered as a limited company in Skien, Telemark with organisation number 916196121. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investeringer i aksjer og eiendommer og hva herved står i naturlig forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 200,000 in revenue and NOK 161,000 in operating profit.

Key figures · 2025

Revenue
NOK 200,000
Operating profit
NOK 161,000
Equity
NOK 723,000
Est. value
NOK 831,000

Financial health · 2025

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

Who owns FLEXI HOLDING AS?

ARILD KOLSTAD
FLEXI HOLDING AS
NOK 200,000 rev. · NOK 161,000 profit

FLEXI HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FLEXI HOLDING AS own?

FLEXI HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FLEXI HOLDING AS

Who owns FLEXI HOLDING AS?

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

What is the revenue of FLEXI HOLDING AS?

FLEXI HOLDING AS had revenue of NOK 200,000 in 2025.

Who is the general manager of FLEXI HOLDING AS?

Arild Kolstad is registered as general manager of FLEXI HOLDING AS.

Where is FLEXI HOLDING AS based?

FLEXI HOLDING AS has its business address in Skien.

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.