biztrac. BETA
COMPANY REGISTER PROFILE
917591695 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

TESFU HOLDING AS

Org. no. 917591695 Limited company (AS) Bærum Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −14,000
Equity NOK −119,000
Incorporated 2016
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−119k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14k kr).

TESFU HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 917591695. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100000 shares. The company's stated purpose is: “Investeringer, eierskap i andre selskaper, rådgivning, foredragsvirksomhet samt alt som står i forbindelse med dette.”.

Former names: KIWENA AS

Key figures · 2025

Operating profit
NOK −14,000
▲ +40 %
Equity
NOK −119,000
▼ −14 %

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-65.9%
Not satisfactory
Return on total assets
Solidity
-549.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns TESFU HOLDING AS?

TESFU HOLDING AS
· NOK −14,000 profit

TESFU HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TESFU HOLDING AS own?

TESFU HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TESFU HOLDING AS

Who owns TESFU HOLDING AS?

Jonas Tesfu is the largest registered owner, with 100.0%.

Who is the general manager of TESFU HOLDING AS?

Jonas Tesfu is registered as general manager of TESFU HOLDING AS.

Where is TESFU HOLDING AS based?

TESFU HOLDING AS has its business address in Lysaker.

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.