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

EIERSEKSJONSSAMEIET SVERDRUPSGATE 22

Org. no. 993300365 Condominium flat owner (ESEK) Oslo Incorporated 2008 Active
Revenue 2025 NOK 939,000
Operating profit NOK 252,000
Equity NOK −1.9m
Incorporated 2008

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,9 mill kr).

EIERSEKSJONSSAMEIET SVERDRUPSGATE 22 is registered as a condominium flat owner in Oslo, Oslo with organisation number 993300365. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2008. The company's stated purpose is: “Ivareta sameiernes fellesinteresser og administrasjon av eiendommen med fellesanlegg av enhver art.”. The most recent filed accounts, for the 2025 financial year, show NOK 939,000 in revenue and NOK 252,000 in operating profit.

Key figures · 2025

Revenue
NOK 939,000
▲ +2 %
Operating profit
NOK 252,000
▼ −2 %
Equity
NOK −1.9m
▲ +6 %
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
59.85
Very good
Current assets ÷ current liabilities
Profitability
59.7%
Very good
Return on total assets
Solidity
-385.2%
Weak
Equity as a share of total capital

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

Who owns EIERSEKSJONSSAMEIET SVERDRUPSGATE 22?

No shareholders are registered for EIERSEKSJONSSAMEIET SVERDRUPSGATE 22 in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about EIERSEKSJONSSAMEIET SVERDRUPSGATE 22

What is the revenue of EIERSEKSJONSSAMEIET SVERDRUPSGATE 22?

EIERSEKSJONSSAMEIET SVERDRUPSGATE 22 had revenue of NOK 939,000 in 2025.

Where is EIERSEKSJONSSAMEIET SVERDRUPSGATE 22 based?

EIERSEKSJONSSAMEIET SVERDRUPSGATE 22 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.