BIZTRAC BETA
Buying and selling of own real estate

ISAVI AS

Org. no. 934929519 Limited company (AS) Trondheim Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK 22,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

ISAVI AS is registered as a limited company in Trondheim, Trøndelag with organisation number 934929519. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen utleie av eiendom og annet som naturlig sammenfaller med dette samt deltakelse i andre selskaper, investeringer og nærliggende 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
Equity
NOK 22,000
Est. value
NOK 20,000

Financial health · 2025

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

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

Who owns ISAVI AS?

ULRIK SOLBERG ISAKSEN
ISAVI AS
NOK 0 rev. · NOK −2,000 profit

ISAVI AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ISAVI AS

Who owns ISAVI AS?

ULRIK SOLBERG ISAKSEN is the largest registered owner, with 80.0%.

What is the revenue of ISAVI AS?

ISAVI AS had revenue of NOK 0 in 2025.

Who is the general manager of ISAVI AS?

Nora Grøtting is registered as general manager of ISAVI AS.

Where is ISAVI AS based?

ISAVI AS has its business address in Trondheim.

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.