BIZTRAC BETA
Wholesale of other machinery and equipment

FIBERGROSSISTEN EMCOM AS

Org. no. 957902065 Limited company (AS) Oslo Incorporated 1990 Active
Ownership graph ↗
Revenue 2025 NOK 35.5m
Operating profit NOK 5.2m
Equity NOK 31.8m
Incorporated 1990
Employees 10
Share capital NOK 500,000

Signals

1 flags
  • Nylig endring 2026-07-08 Avregistrert registrert 2026-07-08.

FIBERGROSSISTEN EMCOM AS is registered as a limited company in Oslo, Oslo with organisation number 957902065. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 1990 and has 10 registered employees. Registered share capital is NOK 500,000, divided into 1000 shares. The company's stated purpose is: “Salg av kommunikasjonsprodukter, egenprodusert og agenturvirksomhet, deltagelse i Eurekaprosjekter, deltagelse i andre selskaper, samt det som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 35.5m in revenue and NOK 5.2m in operating profit.

Key figures · 2025

Revenue
NOK 35.5m
Operating profit
NOK 5.2m
Equity
NOK 31.8m
Est. value
NOK 35.8m

Financial health · 2025

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

Who owns FIBERGROSSISTEN EMCOM AS?

BJØRN MØLLERUD
FIBERGROSSISTEN EMCOM AS
NOK 35.5m rev. · NOK 5.2m profit

FIBERGROSSISTEN EMCOM AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about FIBERGROSSISTEN EMCOM AS

Who owns FIBERGROSSISTEN EMCOM AS?

BJØRN MØLLERUD is the largest registered owner, with 55.0%.

What is the revenue of FIBERGROSSISTEN EMCOM AS?

FIBERGROSSISTEN EMCOM AS had revenue of NOK 35.5m in 2025.

Where is FIBERGROSSISTEN EMCOM AS based?

FIBERGROSSISTEN EMCOM 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.