biztrac. BETA
COMPANY REGISTER PROFILE
930697583 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

PROSJEKTBOLIG AS

Org. no. 930697583 Limited company (AS) Ørsta Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 693,000
Operating profit NOK 149,000
Equity NOK 305,000
Incorporated 2023
Share capital NOK 30,000

PROSJEKTBOLIG AS is registered as a limited company in Ørsta, Møre og Romsdal with organisation number 930697583. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Sal av varer og tenester knytt til oppføring av bygg. Selskapet skal også kunne drive engroshandel og detaljhandel. Selskapet skal kunne kjøpe, eige og selje aksjar eller andelar i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 693,000 in revenue and NOK 149,000 in operating profit.

Key figures · 2025

Revenue
NOK 693,000
▲ +4 %
Operating profit
NOK 149,000
▲ +25 %
Equity
NOK 305,000
▲ +62 %
Est. value
NOK 546,000

Financial health · 2025

Liquidity
3.16
Very good
Current assets ÷ current liabilities
Profitability
30.3%
Very good
Return on total assets
Solidity
68.4%
Very good
Equity as a share of total capital

Who owns PROSJEKTBOLIG AS?

PROSJEKTBOLIG AS
NOK 693,000 rev. · NOK 149,000 profit

PROSJEKTBOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PROSJEKTBOLIG AS

Who owns PROSJEKTBOLIG AS?

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

What is the revenue of PROSJEKTBOLIG AS?

PROSJEKTBOLIG AS had revenue of NOK 693,000 in 2025.

Where is PROSJEKTBOLIG AS based?

PROSJEKTBOLIG AS has its business address in Ørsta.

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.