BIZTRAC BETA
Other technical consultancy

APPLIED COST CUT AS

Org. no. 980644650 Limited company (AS) Froland Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 541,000
Equity NOK 1.0m
Incorporated 1999
Share capital NOK 100,000

APPLIED COST CUT AS is registered as a limited company in Froland, Agder with organisation number 980644650. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Rådgivende ingeniørtjenester hovedsakelig rettet mot olje-relatert virksomhet. Salg av varer og tjenester, deltakelse i andre selskaper og ellers hva som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 541,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 541,000
Equity
NOK 1.0m
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns APPLIED COST CUT AS?

ARNE ROGER EGELAND ARNTZEN
APPLIED COST CUT AS
NOK 1.7m rev. · NOK 541,000 profit

APPLIED COST CUT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about APPLIED COST CUT AS

Who owns APPLIED COST CUT AS?

ARNE ROGER EGELAND ARNTZEN is the largest registered owner, with 100.0%.

What is the revenue of APPLIED COST CUT AS?

APPLIED COST CUT AS had revenue of NOK 1.7m in 2024.

Who is the general manager of APPLIED COST CUT AS?

Arne Roger Egeland Arntzen is registered as general manager of APPLIED COST CUT AS.

Where is APPLIED COST CUT AS based?

APPLIED COST CUT AS has its business address in Froland.

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.