BIZTRAC BETA
Other technical consultancy

FENSLI CONSULTING AS

Org. no. 818751982 Limited company (AS) Arendal Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 16,000
Operating profit NOK −25,000
Equity NOK 2.4m
Incorporated 2017
Share capital NOK 30,000

Signals

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

FENSLI CONSULTING AS is registered as a limited company in Arendal, Agder with organisation number 818751982. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Konsulentvirksomhet og utvikling av e-helse teknologi og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 16,000 in revenue and NOK −25,000 in operating profit.

Key figures · 2025

Revenue
NOK 16,000
Operating profit
NOK −25,000
Equity
NOK 2.4m
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns FENSLI CONSULTING AS?

RUNE WERNER FENSLI
FENSLI CONSULTING AS
NOK 16,000 rev. · NOK −25,000 profit

FENSLI CONSULTING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does FENSLI CONSULTING AS own?

FENSLI CONSULTING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FENSLI CONSULTING AS

Who owns FENSLI CONSULTING AS?

RUNE WERNER FENSLI is the largest registered owner, with 25.0%.

What is the revenue of FENSLI CONSULTING AS?

FENSLI CONSULTING AS had revenue of NOK 16,000 in 2025.

Where is FENSLI CONSULTING AS based?

FENSLI CONSULTING AS has its business address in Færvik.

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.