BIZTRAC BETA
Activities of agents involved in the wholesale of other particular products

INTERCON AS

Org. no. 831210672 Limited company (AS) Trondheim Incorporated 1981 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 305,000
Equity NOK 116,000
Incorporated 1981
Share capital NOK 100,000

INTERCON AS is registered as a limited company in Trondheim, Trøndelag with organisation number 831210672. The business is classified under activities of agents involved in the wholesale of other particular products (NACE 46.180). The company was incorporated in 1981. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Import og handel, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 305,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 305,000
Equity
NOK 116,000
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
1.55
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
38.0%
Good
Equity as a share of total capital

Who owns INTERCON AS?

ENDRE GILSTAD
INTERCON AS
NOK 1.3m rev. · NOK 305,000 profit

INTERCON AS has 1 registered shareholder:

All shareholders and roles →

Which companies does INTERCON AS own?

INTERCON AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about INTERCON AS

Who owns INTERCON AS?

ENDRE GILSTAD is the largest registered owner, with 100.0%.

What is the revenue of INTERCON AS?

INTERCON AS had revenue of NOK 1.3m in 2025.

Who is the general manager of INTERCON AS?

Endre Gilstad is registered as general manager of INTERCON AS.

Where is INTERCON AS based?

INTERCON AS has its business address in Trondheim.

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.