biztrac. BETA
COMPANY REGISTER PROFILE
935795494 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

GRANDAHL BOLIG AS

Org. no. 935795494 Limited company (AS) Sarpsborg Incorporated 2025 Active
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK 93,000
Incorporated 2025
Share capital NOK 100,000

Signals

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

GRANDAHL BOLIG AS is registered as a limited company in Sarpsborg, Østfold with organisation number 935795494. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2025. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Drive kjøp, salg og utleie av egen fast eiendom, inkludert investering, utvikling, forvaltning, salg og utleie av bolig- og næringseiendommer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 93,000
Est. value
NOK 85,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

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

Who owns GRANDAHL BOLIG AS?

GRANDAHL BOLIG AS
NOK 0 rev. · NOK −7,000 profit

GRANDAHL BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRANDAHL BOLIG AS

Who owns GRANDAHL BOLIG AS?

BNG ASSET MANAGEMENT AS is the largest registered owner, with 100.0%.

What is the revenue of GRANDAHL BOLIG AS?

GRANDAHL BOLIG AS had revenue of NOK 0 in 2025.

Where is GRANDAHL BOLIG AS based?

GRANDAHL BOLIG AS has its business address in Hafslundsøy.

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.