BIZTRAC BETA
Development of building projects

PÅSKEDAGSHEIA BOLIG AS

Org. no. 926473409 Limited company (AS) Arendal Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 10.4m
Operating profit NOK 330,000
Equity NOK 52,000
Incorporated 2020
Share capital NOK 30,000

PÅSKEDAGSHEIA BOLIG AS is registered as a limited company in Arendal, Agder with organisation number 926473409. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og utvikling av tomter, samt oppføring og salg av boliger og virksomhet som står i tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.4m in revenue and NOK 330,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.4m
Operating profit
NOK 330,000
Equity
NOK 52,000
Est. value
NOK 426,000

Financial health · 2024

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

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

Who owns PÅSKEDAGSHEIA BOLIG AS?

NEDENES VEKST AS
PÅSKEDAGSHEIA BOLIG AS
NOK 10.4m rev. · NOK 330,000 profit

PÅSKEDAGSHEIA BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PÅSKEDAGSHEIA BOLIG AS

Who owns PÅSKEDAGSHEIA BOLIG AS?

NEDENES VEKST AS is the largest registered owner, with 100.0%.

What is the revenue of PÅSKEDAGSHEIA BOLIG AS?

PÅSKEDAGSHEIA BOLIG AS had revenue of NOK 10.4m in 2024.

Who is the general manager of PÅSKEDAGSHEIA BOLIG AS?

Bjørn Magne Hansen is registered as general manager of PÅSKEDAGSHEIA BOLIG AS.

Where is PÅSKEDAGSHEIA BOLIG AS based?

PÅSKEDAGSHEIA BOLIG AS has its business address in Arendal.

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.