BIZTRAC BETA
Wired, wireless, and satellite telecommunication activities

FINCOM AS

Org. no. 918626735 Limited company (AS) Alta Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −42,000
Equity NOK 768,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

FINCOM AS is registered as a limited company in Alta, Finnmark with organisation number 918626735. The business is classified under wired, wireless, and satellite telecommunication activities (NACE 61.100). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulenttjenester innen telekommunikasjon samt montasje og drift av telekommunikasjonsutstyr, utleie av arbeidskraft, investering i næringssvirksomhet, herunder aksjer og andeler, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −42,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −42,000
Equity
NOK 768,000
Est. value
NOK 1.9m

Financial health · 2025

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

Who owns FINCOM AS?

BJØRN TRYGVE PAULSEN
FINCOM AS
NOK 0 rev. · NOK −42,000 profit

FINCOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FINCOM AS

Who owns FINCOM AS?

BJØRN TRYGVE PAULSEN is the largest registered owner, with 100.0%.

What is the revenue of FINCOM AS?

FINCOM AS had revenue of NOK 0 in 2025.

Who is the general manager of FINCOM AS?

Bjørn Trygve Paulsen is registered as general manager of FINCOM AS.

Where is FINCOM AS based?

FINCOM AS has its business address in Alta.

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.