biztrac. BETA
COMPANY REGISTER PROFILE
998805856 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Manufacture of concrete products for construction purposes

SKARPNES AS

Org. no. 998805856 Limited company (AS) Grimstad Incorporated 2012 Active
Revenue 2025 NOK 239.0m
Operating profit NOK 34.6m
Equity NOK 46.0m
Incorporated 2012
Employees 57
Share capital NOK 2.0m

SKARPNES AS is registered as a limited company in Grimstad, Agder with organisation number 998805856. The business is classified under manufacture of concrete products for construction purposes (NACE 23.610). The company was incorporated in 2012 and has 57 registered employees. Registered share capital is NOK 2.0m, divided into 2025 shares. The company's stated purpose is: “Produksjon, handel og annen økonomisk virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 239.0m in revenue and NOK 34.6m in operating profit.

Former names: SKARPNES DRIFT AS

Key figures · 2025

Revenue
NOK 239.0m
▲ +50 %
Operating profit
NOK 34.6m
▲ +211 %
Equity
NOK 46.0m
▼ −1 %
Est. value
NOK 119.9m

Financial health · 2025

Liquidity
1.51
Good
Current assets ÷ current liabilities
Profitability
32.4%
Very good
Return on total assets
Solidity
36.9%
Good
Equity as a share of total capital

Who owns SKARPNES AS?

SKARPNES AS
NOK 239.0m rev. · NOK 34.6m profit

SKARPNES AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SKARPNES AS er morselskap for 1 datterselskap:

Frequently asked questions about SKARPNES AS

Who owns SKARPNES AS?

SKARPNES HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SKARPNES AS?

SKARPNES AS had revenue of NOK 239.0m in 2025.

Who is the general manager of SKARPNES AS?

Jørn Tveite is registered as general manager of SKARPNES AS.

Where is SKARPNES AS based?

SKARPNES AS has its business address in Grimstad.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.