biztrac. BETA
COMPANY REGISTER PROFILE
935726808 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

STEINSFJORDEN EIENDOM BOLIG AS

Org. no. 935726808 Limited company (AS) Drammen Incorporated 2025 Active
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 20,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

STEINSFJORDEN EIENDOM BOLIG AS is registered as a limited company in Drammen, Buskerud with organisation number 935726808. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i aksjer og verdipapirer, selskaper, selskapsandeler og fast eiendom samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Former names: NFH 250690 AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 20,000
Est. value
NOK 24,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 STEINSFJORDEN EIENDOM BOLIG AS?

No shareholders are registered for STEINSFJORDEN EIENDOM BOLIG AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about STEINSFJORDEN EIENDOM BOLIG AS

What is the revenue of STEINSFJORDEN EIENDOM BOLIG AS?

STEINSFJORDEN EIENDOM BOLIG AS had revenue of NOK 0 in 2025.

Where is STEINSFJORDEN EIENDOM BOLIG AS based?

STEINSFJORDEN EIENDOM BOLIG AS has its business address in Drammen.

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.