BIZTRAC BETA
Other captive investment companies

EVISE AS

Org. no. 989032836 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −24,000
Equity NOK 16.1m
Incorporated 2005
Share capital NOK 450,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−24k kr).

EVISE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 989032836. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 450,000, divided into 25 shares. The company's stated purpose is: “Selskapets formål er å eie aksjer i begravelsesbyrå og beslektet virksomhet. Selskapet kan også plassere ledig kapital i eiendom eller verdipapirer. ”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −24,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −24,000
Equity
NOK 16.1m
Est. value
NOK 15.9m

Financial health · 2024

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

Who owns EVISE AS?

CHRISTIAN SVANHOLM
EVISE AS
NOK 0 rev. · NOK −24,000 profit

EVISE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EVISE AS own?

EVISE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about EVISE AS

Who owns EVISE AS?

CHRISTIAN SVANHOLM is the largest registered owner, with 100.0%.

What is the revenue of EVISE AS?

EVISE AS had revenue of NOK 0 in 2024.

Who is the general manager of EVISE AS?

Christian Svanholm is registered as general manager of EVISE AS.

Where is EVISE AS based?

EVISE AS has its business address in Saupstad.

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.