biztrac. BETA
COMPANY REGISTER PROFILE
980650995 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of housing cooperatives

SAMEIET ERLING SKJALGSSONSGATE 30

Org. no. 980650995 Condominium flat owner (ESEK) Oslo Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 810,000
Operating profit NOK 74,000
Equity NOK −403,000
Incorporated 1996

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−403k kr).

SAMEIET ERLING SKJALGSSONSGATE 30 is registered as a condominium flat owner in Oslo, Oslo with organisation number 980650995. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1996. The company's stated purpose is: “Å ivareta sameiernes fellesinteresser og administrasjon av eiendommen, gnr 212 bnr 285 i Oslo med fellesanlegg av enhver art.”. The most recent filed accounts, for the 2025 financial year, show NOK 810,000 in revenue and NOK 74,000 in operating profit.

Key figures · 2025

Revenue
NOK 810,000
▲ +8 %
Operating profit
NOK 74,000
▼ −3 %
Equity
NOK −403,000
▲ +11 %
Est. value
NOK 410,000

Financial health · 2025

Liquidity
4.45
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-157.6%
Weak
Equity as a share of total capital

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

Who owns SAMEIET ERLING SKJALGSSONSGATE 30?

No shareholders are registered for SAMEIET ERLING SKJALGSSONSGATE 30 in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SAMEIET ERLING SKJALGSSONSGATE 30

What is the revenue of SAMEIET ERLING SKJALGSSONSGATE 30?

SAMEIET ERLING SKJALGSSONSGATE 30 had revenue of NOK 810,000 in 2025.

Where is SAMEIET ERLING SKJALGSSONSGATE 30 based?

SAMEIET ERLING SKJALGSSONSGATE 30 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.