biztrac. BETA
COMPANY REGISTER PROFILE
935587611 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

ISTINVEST AS

Org. no. 935587611 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −17,000
Equity NOK −18,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

ISTINVEST AS is registered as a limited company in Oslo, Oslo with organisation number 935587611. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjeselskaper og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −17,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −17,000
▲ +0 %
Equity
NOK −18,000
▼ −241 %

Financial health · 2025

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

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

Who owns ISTINVEST AS?

ISTINVEST AS
NOK 0 rev. · NOK −17,000 profit

ISTINVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ISTINVEST AS own?

ISTINVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ISTINVEST AS

Who owns ISTINVEST AS?

Bendek Maartmann-Moe is the largest registered owner, with 100.0%.

What is the revenue of ISTINVEST AS?

ISTINVEST AS had revenue of NOK 0 in 2025.

Where is ISTINVEST AS based?

ISTINVEST AS has its business address in Oslo.

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.