BIZTRAC BETA
Research and experimental development on natural sciences and engineering

DRAUPNIR KAPITAL AS

Org. no. 816674492 Limited company (AS) Ullensaker Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK −224,000
Incorporated 2016
Share capital NOK 80,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−224k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5k kr).

DRAUPNIR KAPITAL AS is registered as a limited company in Ullensaker, Akershus with organisation number 816674492. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2016. Registered share capital is NOK 80,000, divided into 150 shares. The company's stated purpose is: “Utvikle og selge kommunikasjonsløsninger innen telekommunikasjon, internett og andre kommunikasjonsområder. I tillegg skal selskapet drive med investering i finansaktiva.”.

Key figures · 2024

Operating profit
NOK −5,000
Equity
NOK −224,000

Financial health · 2024

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

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

Who owns DRAUPNIR KAPITAL AS?

MAGNUS NÆSBU FJÆRLI
DRAUPNIR KAPITAL AS
· NOK −5,000 profit

DRAUPNIR KAPITAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DRAUPNIR KAPITAL AS own?

DRAUPNIR KAPITAL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DRAUPNIR KAPITAL AS

Who owns DRAUPNIR KAPITAL AS?

MAGNUS NÆSBU FJÆRLI is the largest registered owner, with 100.0%.

Where is DRAUPNIR KAPITAL AS based?

DRAUPNIR KAPITAL AS has its business address in Jessheim.

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

Report a problem

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