BIZTRAC BETA
COMPANY REGISTER PROFILE
936068499 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

TWIRLCAP AS

Org. no. 936068499 Limited company (AS) Bærum Incorporated 2025 Active
Ownership graph ↗
Equity NOK 21,000
Incorporated 2025
Share capital NOK 30,000

TWIRLCAP AS is registered as a limited company in Bærum, Akershus with organisation number 936068499. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i aksjer, fond, og andre finansielle instrumenter, samt annen virksomhet som står i naturlig forbindelse med dette.”.

Key figures · 2025

Equity
NOK 21,000
Est. value
NOK 24,000

Financial health · 2025

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

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

Who owns TWIRLCAP AS?

TWIRLCAP AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TWIRLCAP AS own?

TWIRLCAP AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TWIRLCAP AS

Who owns TWIRLCAP AS?

MARTINE THORVILDSEN WIRSCHING is the largest registered owner, with 100.0%.

Where is TWIRLCAP AS based?

TWIRLCAP AS has its business address in Bekkestua.

Property

Business address Ringkroken 20A, 1356 Bekkestua
Cadastral unit 3201-17/680/0/0
Building Tomannsbolig, vertikal · 1 unit

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.