biztrac. BETA
COMPANY REGISTER PROFILE
964298521 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other business support service activities n.e.c.

INNSAMLINGSKONTROLLEN I NORGE STI

Org. no. 964298521 Foundation (STI) Oslo Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 3.8m
Operating profit NOK 200,000
Equity NOK 3.1m
Incorporated 1991
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-07-07 Adresseendring registrert 2026-07-07.

INNSAMLINGSKONTROLLEN I NORGE STI is registered as a foundation in Oslo, Oslo with organisation number 964298521. The business is classified under other business support service activities n.e.c. (NACE 82.990). The company was incorporated in 1991. Registered share capital is NOK 100,000. The most recent filed accounts, for the 2025 financial year, show NOK 3.8m in revenue and NOK 200,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.8m
▲ +37 %
Operating profit
NOK 200,000
▲ +142 %
Equity
NOK 3.1m
▲ +9 %
Est. value
NOK 3.5m

Financial health · 2025

Liquidity
8.55
Very good
Current assets ÷ current liabilities
Profitability
7.3%
Satisfactory
Return on total assets
Solidity
88.3%
Very good
Equity as a share of total capital

Who owns INNSAMLINGSKONTROLLEN I NORGE STI?

No shareholders are registered for INNSAMLINGSKONTROLLEN I NORGE STI in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about INNSAMLINGSKONTROLLEN I NORGE STI

What is the revenue of INNSAMLINGSKONTROLLEN I NORGE STI?

INNSAMLINGSKONTROLLEN I NORGE STI had revenue of NOK 3.8m in 2025.

Who is the general manager of INNSAMLINGSKONTROLLEN I NORGE STI?

Ronny Fredrik Sandvik is registered as general manager of INNSAMLINGSKONTROLLEN I NORGE STI.

Where is INNSAMLINGSKONTROLLEN I NORGE STI based?

INNSAMLINGSKONTROLLEN I NORGE STI 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.