biztrac. BETA
COMPANY REGISTER PROFILE
935727286 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Geological surveying

RUNWAY EXPLORATION AS

Org. no. 935727286 Limited company (AS) Bærum Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −11,000
Equity NOK 19,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RUNWAY EXPLORATION AS is registered as a limited company in Bærum, Akershus with organisation number 935727286. The business is classified under geological surveying (NACE 71.122). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Mineral prospektering.”.

Former names: NFH 250657 AS

Key figures · 2025

Operating profit
NOK −11,000
Equity
NOK 19,000
Est. value
NOK 30,000

Financial health · 2025

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

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

Who owns RUNWAY EXPLORATION AS?

ALPHA FUTURE FUNDS S.C.S LU
RUNWAY EXPLORATION AS
· NOK −11,000 profit

RUNWAY EXPLORATION AS has 1 registered shareholder:

  • ALPHA FUTURE FUNDS S.C.S 100.0%
All shareholders and roles →

Frequently asked questions about RUNWAY EXPLORATION AS

Who owns RUNWAY EXPLORATION AS?

ALPHA FUTURE FUNDS S.C.S is the largest registered owner, with 100.0%.

Who is the general manager of RUNWAY EXPLORATION AS?

Johannes Holzäpfel is registered as general manager of RUNWAY EXPLORATION AS.

Where is RUNWAY EXPLORATION AS based?

RUNWAY EXPLORATION AS has its business address in Lysaker.

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.