biztrac. BETA
COMPANY REGISTER PROFILE
836965752 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 03.10.2026
⚠GULSKOGEN STASJON 4 BOLIG AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Uoppgitt

GULSKOGEN STASJON 4 BOLIG AS

Org. no. 836965752 Limited company (AS) Oslo Incorporated 2025 In liquidation
Ownership graph ↗
Equity NOK 30,000
Incorporated 2025
Share capital NOK 30,000

Signals

3 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nystiftet selskap Selskapet ble stiftet 2025-12-17.

GULSKOGEN STASJON 4 BOLIG AS is registered as a limited company in Oslo, Oslo with organisation number 836965752. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i fast eiendom eller eierandeler i selskaper som direkte eller indirekte eier fast eiendom, verdipapirer samt annen virksomhet i tilknytning til dette.”.

Key figures · 2025

Equity
NOK 30,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 GULSKOGEN STASJON 4 BOLIG AS?

GULSKOGEN STASJON 4 BOLIG AS

GULSKOGEN STASJON 4 BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GULSKOGEN STASJON 4 BOLIG AS

Who owns GULSKOGEN STASJON 4 BOLIG AS?

SENTRALTIND INVEST 6 AS is the largest registered owner, with 100.0%.

Where is GULSKOGEN STASJON 4 BOLIG AS based?

GULSKOGEN STASJON 4 BOLIG 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.