BIZTRAC BETA
Wholesale of agricultural machinery, equipment and supplies

KRISTIANSAND ANLEGGSENTER AS

Org. no. 931523635 Limited company (AS) Kristiansand Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 752,000
Operating profit NOK 30,000
Equity NOK 186,000
Incorporated 2023
Share capital NOK 500,000

KRISTIANSAND ANLEGGSENTER AS is registered as a limited company in Kristiansand, Agder with organisation number 931523635. The business is classified under wholesale of agricultural machinery, equipment and supplies (NACE 46.610). The company was incorporated in 2023. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Salg av traktor, maskiner og utstyr.”. The most recent filed accounts, for the 2025 financial year, show NOK 752,000 in revenue and NOK 30,000 in operating profit.

Key figures · 2025

Revenue
NOK 752,000
Operating profit
NOK 30,000
Equity
NOK 186,000
Est. value
NOK 236,000

Financial health · 2025

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

Who owns KRISTIANSAND ANLEGGSENTER AS?

TM NORGE AS
KRISTIANSAND ANLEGGSENTER AS
NOK 752,000 rev. · NOK 30,000 profit

KRISTIANSAND ANLEGGSENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KRISTIANSAND ANLEGGSENTER AS

Who owns KRISTIANSAND ANLEGGSENTER AS?

TM NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of KRISTIANSAND ANLEGGSENTER AS?

KRISTIANSAND ANLEGGSENTER AS had revenue of NOK 752,000 in 2025.

Who is the general manager of KRISTIANSAND ANLEGGSENTER AS?

Trond Widar Løyning is registered as general manager of KRISTIANSAND ANLEGGSENTER AS.

Where is KRISTIANSAND ANLEGGSENTER AS based?

KRISTIANSAND ANLEGGSENTER AS has its business address in Mosby.

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.