BIZTRAC BETA
Wired, wireless, and satellite telecommunication activities

BULK FIBER NETWORKS AS

Org. no. 816269822 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −15.8m
Equity NOK 729.0m
Incorporated 2015
Share capital NOK 1.4m

Signals

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

BULK FIBER NETWORKS AS is registered as a limited company in Oslo, Oslo with organisation number 816269822. The business is classified under wired, wireless, and satellite telecommunication activities (NACE 61.100). The company was incorporated in 2015. Registered share capital is NOK 1.4m, divided into 474630 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeid med andre virksomheter å utvikle, drifte og selge fiberinfrastruktur, samt tilknyttet virksomhet.”.

Key figures · 2024

Operating profit
NOK −15.8m
Equity
NOK 729.0m
Est. value
NOK 407.9m

Financial health · 2024

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

Who owns BULK FIBER NETWORKS AS?

BULK INFRASTRUCTURE GROUP AS
BULK FIBER NETWORKS AS
· NOK −15.8m profit

BULK FIBER NETWORKS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BULK FIBER NETWORKS AS own?

BULK FIBER NETWORKS AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about BULK FIBER NETWORKS AS

Who owns BULK FIBER NETWORKS AS?

BULK INFRASTRUCTURE GROUP AS is the largest registered owner, with 100.0%.

Where is BULK FIBER NETWORKS AS based?

BULK FIBER NETWORKS AS has its business address in Oslo.

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.