BIZTRAC BETA
Computer programming activities

BIFROST OG DRAUPNE AS

Org. no. 914721091 Limited company (AS) Haugesund Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 5.3m
Operating profit NOK −1.9m
Equity NOK 403.1m
Incorporated 2014
Share capital NOK 300,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,9 mill kr).

BIFROST OG DRAUPNE AS is registered as a limited company in Haugesund, Rogaland with organisation number 914721091. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2014. Registered share capital is NOK 300,000, divided into 299998 shares. The company's stated purpose is: “Investere i aksjer, verdipapirer og andre selskapsandeler, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.3m in revenue and NOK −1.9m in operating profit.

Key figures · 2024

Revenue
NOK 5.3m
Operating profit
NOK −1.9m
Equity
NOK 403.1m
Est. value
NOK 445.9m

Financial health · 2024

Liquidity
20.14
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.1%
Good
Equity as a share of total capital

Who owns BIFROST OG DRAUPNE AS?

SERA AS
BIFROST OG DRAUPNE AS
NOK 5.3m rev. · NOK −1.9m profit

BIFROST OG DRAUPNE AS has 4 registered shareholders:

All shareholders and roles →

Which companies does BIFROST OG DRAUPNE AS own?

BIFROST OG DRAUPNE AS holds stakes in 22 companies:

See the full ownership structure →

Frequently asked questions about BIFROST OG DRAUPNE AS

Who owns BIFROST OG DRAUPNE AS?

SERA AS is the largest registered owner, with 30.1%.

What is the revenue of BIFROST OG DRAUPNE AS?

BIFROST OG DRAUPNE AS had revenue of NOK 5.3m in 2024.

Where is BIFROST OG DRAUPNE AS based?

BIFROST OG DRAUPNE AS has its business address in Haugesund.

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.