BIZTRAC BETA
Other telecommunication activities

BIGBEAR COMMUNICATIONS AS

Org. no. 989131230 Limited company (AS) Frogn Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 618
Operating profit NOK −11,000
Equity NOK 187,000
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11k kr).

BIGBEAR COMMUNICATIONS AS is registered as a limited company in Frogn, Akershus with organisation number 989131230. The business is classified under other telecommunication activities (NACE 61.900). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utvikling og drift av IKT-tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 618 in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 618
Operating profit
NOK −11,000
Equity
NOK 187,000
Est. value
NOK 163,000

Financial health · 2025

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

Who owns BIGBEAR COMMUNICATIONS AS?

BJØRN TORJE TVEITEN
BIGBEAR COMMUNICATIONS AS
NOK 618 rev. · NOK −11,000 profit

BIGBEAR COMMUNICATIONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BIGBEAR COMMUNICATIONS AS

Who owns BIGBEAR COMMUNICATIONS AS?

BJØRN TORJE TVEITEN is the largest registered owner, with 100.0%.

What is the revenue of BIGBEAR COMMUNICATIONS AS?

BIGBEAR COMMUNICATIONS AS had revenue of NOK 618 in 2025.

Who is the general manager of BIGBEAR COMMUNICATIONS AS?

Bjørn Torje Tveiten is registered as general manager of BIGBEAR COMMUNICATIONS AS.

Where is BIGBEAR COMMUNICATIONS AS based?

BIGBEAR COMMUNICATIONS AS has its business address in Drøbak.

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.