biztrac. BETA
COMPANY REGISTER PROFILE
831690542 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

WOLFIE CAPITAL AS

Org. no. 831690542 Limited company (AS) Lillestrøm Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −3,000
Equity NOK 4,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

WOLFIE CAPITAL AS is registered as a limited company in Lillestrøm, Akershus with organisation number 831690542. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie verdipapirer i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK −3,000
▼ −136 %
Equity
NOK 4,000
▼ −39 %
Est. value
NOK 5,000

Financial health · 2025

Liquidity
5.95
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
3.4%
Weak
Equity as a share of total capital

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

Who owns WOLFIE CAPITAL AS?

WOLFIE CAPITAL AS
NOK 0 rev. · NOK −3,000 profit

WOLFIE CAPITAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does WOLFIE CAPITAL AS own?

WOLFIE CAPITAL AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about WOLFIE CAPITAL AS

Who owns WOLFIE CAPITAL AS?

August Enger Sandmo is the largest registered owner, with 100.0%.

What is the revenue of WOLFIE CAPITAL AS?

WOLFIE CAPITAL AS had revenue of NOK 0 in 2025.

Where is WOLFIE CAPITAL AS based?

WOLFIE CAPITAL AS has its business address in Frogner.

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.