BIZTRAC BETA
Wholesale of information and communication equipment

JA TAKK KONTOR AS

Org. no. 980300471 Limited company (AS) Vefsn Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 5.3m
Operating profit NOK −135,000
Equity NOK 1.4m
Incorporated 1998
Share capital NOK 150,000

Signals

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

JA TAKK KONTOR AS is registered as a limited company in Vefsn, Nordland with organisation number 980300471. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 1998. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Salg og service av kontormaskiner, kontormøbler og kontorrekvisita, samt eventuelt å delta i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.3m in revenue and NOK −135,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.3m
Operating profit
NOK −135,000
Equity
NOK 1.4m
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns JA TAKK KONTOR AS?

SALHUS EIENDOM AS
JA TAKK KONTOR AS
NOK 5.3m rev. · NOK −135,000 profit

JA TAKK KONTOR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JA TAKK KONTOR AS

Who owns JA TAKK KONTOR AS?

SALHUS EIENDOM AS is the largest registered owner, with 70.0%.

What is the revenue of JA TAKK KONTOR AS?

JA TAKK KONTOR AS had revenue of NOK 5.3m in 2025.

Who is the general manager of JA TAKK KONTOR AS?

Tommy Sandmo is registered as general manager of JA TAKK KONTOR AS.

Where is JA TAKK KONTOR AS based?

JA TAKK KONTOR AS has its business address in Mosjøen.

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.