BIZTRAC BETA
Rental and operating of own or leased real estate

NETWORKING AS

Org. no. 947817418 Limited company (AS) Bærum Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK 906,000
Equity NOK 9.2m
Incorporated 1988
Share capital NOK 150,000

NETWORKING AS is registered as a limited company in Bærum, Akershus with organisation number 947817418. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1988. Registered share capital is NOK 150,000, divided into 500 shares. The company's stated purpose is: “Å drive handel, eiendomsbesittelse og drifting av fast eiendom, samt deltakelse i andre selskaper og investering i verdipapirer.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK 906,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK 906,000
Equity
NOK 9.2m
Est. value
NOK 9.3m

Financial health · 2024

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

Who owns NETWORKING AS?

BOYD HAAKON HERMANSEN
NETWORKING AS
NOK 2.0m rev. · NOK 906,000 profit

NETWORKING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NETWORKING AS own?

NETWORKING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NETWORKING AS

Who owns NETWORKING AS?

BOYD HAAKON HERMANSEN is the largest registered owner, with 100.0%.

What is the revenue of NETWORKING AS?

NETWORKING AS had revenue of NOK 2.0m in 2024.

Who is the general manager of NETWORKING AS?

Boyd Haakon Hermansen is registered as general manager of NETWORKING AS.

Where is NETWORKING AS based?

NETWORKING AS has its business address in Snarøya.

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.