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

BOLIG FOR FOLKET AS

Org. no. 822067662 Limited company (AS) Rælingen Incorporated 2018 Active
Revenue 2025 NOK 34.5m
Operating profit NOK 3.5m
Equity NOK 5.7m
Incorporated 2018
Share capital NOK 220,000

BOLIG FOR FOLKET AS is registered as a limited company in Rælingen, Akershus with organisation number 822067662. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2018. Registered share capital is NOK 220,000, divided into 200 shares. The company's stated purpose is: “Eiendomsutvikling, boligbygging for videresalg, investering i og utleie av fast eiendom, samt deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 34.5m in revenue and NOK 3.5m in operating profit.

Key figures · 2025

Revenue
NOK 34.5m
Operating profit
NOK 3.5m
▲ +958 %
Equity
NOK 5.7m
▲ +2 %
Est. value
NOK 10.6m

Financial health · 2025

Liquidity
2.69
Very good
Current assets ÷ current liabilities
Profitability
13.7%
Good
Return on total assets
Solidity
63.2%
Very good
Equity as a share of total capital

Who owns BOLIG FOR FOLKET AS?

BOLIG FOR FOLKET AS
NOK 34.5m rev. · NOK 3.5m profit

BOLIG FOR FOLKET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOLIG FOR FOLKET AS

Who owns BOLIG FOR FOLKET AS?

BOLIG FOR FOLKET HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BOLIG FOR FOLKET AS?

BOLIG FOR FOLKET AS had revenue of NOK 34.5m in 2025.

Who is the general manager of BOLIG FOR FOLKET AS?

Roger Rasmussen is registered as general manager of BOLIG FOR FOLKET AS.

Where is BOLIG FOR FOLKET AS based?

BOLIG FOR FOLKET 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.