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

FANGORN KAPITAL AS

Org. no. 936865178 Limited company (AS) Rælingen Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 22,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-12-18.

FANGORN KAPITAL AS is registered as a limited company in Rælingen, Akershus with organisation number 936865178. 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 aksjer og selskaper og andre produkter/tjenester som naturlig hører sammen.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 22,000
Est. value
NOK 26,000

Financial health · 2025

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

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

Who owns FANGORN KAPITAL AS?

FANGORN KAPITAL AS
NOK 0 rev. · NOK 0 profit

FANGORN KAPITAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FANGORN KAPITAL AS own?

FANGORN KAPITAL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FANGORN KAPITAL AS

Who owns FANGORN KAPITAL AS?

Tomasz Grzegorz Jedrusik is the largest registered owner, with 100.0%.

What is the revenue of FANGORN KAPITAL AS?

FANGORN KAPITAL AS had revenue of NOK 0 in 2025.

Where is FANGORN KAPITAL AS based?

FANGORN KAPITAL AS has its business address in Blystadlia.

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.