biztrac. BETA
COMPANY REGISTER PROFILE
916776012 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

FORANDRE BOLIGUTVIKLING AS

Org. no. 916776012 Limited company (AS) Rælingen Incorporated 2016 Active
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK 243,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−13k kr).

FORANDRE BOLIGUTVIKLING AS is registered as a limited company in Rælingen, Akershus with organisation number 916776012. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og oppgradering av boliger. Utfører ulike vedlikeholdsoppdrag knyttet til bolig.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK −13,000
▲ +15 %
Equity
NOK 243,000
▼ −5 %
Est. value
NOK 221,000

Financial health · 2025

Liquidity
14.99
Very good
Current assets ÷ current liabilities
Profitability
-5.0%
Not satisfactory
Return on total assets
Solidity
93.8%
Very good
Equity as a share of total capital

Who owns FORANDRE BOLIGUTVIKLING AS?

FORANDRE BOLIGUTVIKLING AS
NOK 0 rev. · NOK −13,000 profit

FORANDRE BOLIGUTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FORANDRE BOLIGUTVIKLING AS

Who owns FORANDRE BOLIGUTVIKLING AS?

Per Jørgen Gram-Hallbert is the largest registered owner, with 100.0%.

What is the revenue of FORANDRE BOLIGUTVIKLING AS?

FORANDRE BOLIGUTVIKLING AS had revenue of NOK 0 in 2025.

Where is FORANDRE BOLIGUTVIKLING AS based?

FORANDRE BOLIGUTVIKLING AS has its business address in Fjerdingby.

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.