biztrac. BETA
COMPANY REGISTER PROFILE
992052864 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other real estate activities on a fee or contract basis

GRAN BOLIGBYGG AS

Org. no. 992052864 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Operating profit NOK −151,000
Equity NOK 123,000
Incorporated 2007
Share capital NOK 112,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−151k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GRAN BOLIGBYGG AS is registered as a limited company in Oslo, Oslo with organisation number 992052864. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2007. Registered share capital is NOK 112,000, divided into 112314 shares. The company's stated purpose is: “Kjøp, ledelse, forvaltning og utvikling av fast eiendom, herunder deltagelse i andre selskaper og alt som står i forbindelse med det.”.

Key figures · 2025

Operating profit
NOK −151,000
▼ −110 %
Equity
NOK 123,000
▲ +0 %
Est. value
NOK 112,000

Financial health · 2025

Liquidity
4.99
Very good
Current assets ÷ current liabilities
Profitability
-14.1%
Not satisfactory
Return on total assets
Solidity
11.1%
Satisfactory
Equity as a share of total capital

Who owns GRAN BOLIGBYGG AS?

GRAN BOLIGBYGG AS
· NOK −151,000 profit

GRAN BOLIGBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRAN BOLIGBYGG AS

Who owns GRAN BOLIGBYGG AS?

MØLLER EIENDOM NORGE AS is the largest registered owner, with 100.0%.

Who is the general manager of GRAN BOLIGBYGG AS?

Thomas Sletten is registered as general manager of GRAN BOLIGBYGG AS.

Where is GRAN BOLIGBYGG AS based?

GRAN BOLIGBYGG AS has its business address in Oslo.

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.