BIZTRAC BETA
Repair and maintenance of machinery

A.ANLEGGS TEKNIKK AS

Org. no. 934939964 Limited company (AS) Farsund Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 44,000
Equity NOK 64,000
Incorporated 2025
Share capital NOK 30,000

A.ANLEGGS TEKNIKK AS is registered as a limited company in Farsund, Agder with organisation number 934939964. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Reparasjon av maskiner til landbruk/skogbruk, bygg- og anlegg og industri ellers samt annet som naturlig hører til.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 44,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 44,000
Equity
NOK 64,000
Est. value
NOK 195,000

Financial health · 2025

Liquidity
1.31
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns A.ANLEGGS TEKNIKK AS?

STEFFEN TJELLAND ANDREASSEN
A.ANLEGGS TEKNIKK AS
NOK 1.5m rev. · NOK 44,000 profit

A.ANLEGGS TEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about A.ANLEGGS TEKNIKK AS

Who owns A.ANLEGGS TEKNIKK AS?

STEFFEN TJELLAND ANDREASSEN is the largest registered owner, with 100.0%.

What is the revenue of A.ANLEGGS TEKNIKK AS?

A.ANLEGGS TEKNIKK AS had revenue of NOK 1.5m in 2025.

Who is the general manager of A.ANLEGGS TEKNIKK AS?

Steffen Tjelland Andreassen is registered as general manager of A.ANLEGGS TEKNIKK AS.

Where is A.ANLEGGS TEKNIKK AS based?

A.ANLEGGS TEKNIKK AS has its business address in Borhaug.

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.