biztrac. BETA
COMPANY REGISTER PROFILE
914595312 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

SKRAPEKLEV AREAL AS

Org. no. 914595312 Limited company (AS) Porsgrunn Incorporated 2014 Active
Revenue 2025 NOK 1.6m
Operating profit NOK 901,000
Equity NOK 77,000
Incorporated 2014
Share capital NOK 30,000

SKRAPEKLEV AREAL AS is registered as a limited company in Porsgrunn, Telemark with organisation number 914595312. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, utvikling, utleie, drift og salg av fast eiendom, samt deltagelse i andre selskaper, og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 901,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
▲ +14 %
Operating profit
NOK 901,000
▲ +27 %
Equity
NOK 77,000
▼ −25 %
Est. value
NOK 2.0m

Financial health · 2025

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
15.8%
Very good
Return on total assets
Solidity
1.4%
Weak
Equity as a share of total capital

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

Who owns SKRAPEKLEV AREAL AS?

SKRAPEKLEV AREAL AS
NOK 1.6m rev. · NOK 901,000 profit

SKRAPEKLEV AREAL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKRAPEKLEV AREAL AS

Who owns SKRAPEKLEV AREAL AS?

HERØYA LEGESENTER AS is the largest registered owner, with 100.0%.

What is the revenue of SKRAPEKLEV AREAL AS?

SKRAPEKLEV AREAL AS had revenue of NOK 1.6m in 2025.

Where is SKRAPEKLEV AREAL AS based?

SKRAPEKLEV AREAL AS has its business address in Porsgrunn.

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.