BIZTRAC BETA
COMPANY REGISTER PROFILE
984850298 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

SKRIPELAND OG HEIA EIENDOM AS

Org. no. 984850298 Limited company (AS) Birkenes Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 330,000
Operating profit NOK 83,000
Equity NOK 2.1m
Incorporated 2002
Share capital NOK 112,000

SKRIPELAND OG HEIA EIENDOM AS is registered as a limited company in Birkenes, Agder with organisation number 984850298. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 112,000, divided into 112 shares. The company's stated purpose is: “Investere i og drive utleie av fast eiendom, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 330,000 in revenue and NOK 83,000 in operating profit.

Key figures · 2025

Revenue
NOK 330,000
▲ +106 %
Operating profit
NOK 83,000
▲ +195 %
Equity
NOK 2.1m
▲ +2 %
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
0.29
Not satisfactory
Current assets ÷ current liabilities
Profitability
2.8%
Weak
Return on total assets
Solidity
71.6%
Very good
Equity as a share of total capital

Who owns SKRIPELAND OG HEIA EIENDOM AS?

SKRIPELAND OG HEIA EIENDOM AS
NOK 330,000 rev. · NOK 83,000 profit

SKRIPELAND OG HEIA EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SKRIPELAND OG HEIA EIENDOM AS

Who owns SKRIPELAND OG HEIA EIENDOM AS?

PH ENERGI AS is the largest registered owner, with 50.0%.

What is the revenue of SKRIPELAND OG HEIA EIENDOM AS?

SKRIPELAND OG HEIA EIENDOM AS had revenue of NOK 330,000 in 2025.

Where is SKRIPELAND OG HEIA EIENDOM AS based?

SKRIPELAND OG HEIA EIENDOM AS has its business address in Birkeland.

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

Report a problem

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