BIZTRAC BETA
Activities of housing cooperatives

AS VIDARSGATE 13

Org. no. 931086707 Limited company (AS) Oslo Incorporated 1930 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK −384,000
Equity NOK −1.3m
Incorporated 1930
Share capital NOK 100,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,3 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−384k kr).
  • Nylig endring 2026-06-30 Adresseendring registrert 2026-06-30.

AS VIDARSGATE 13 is registered as a limited company in Oslo, Oslo with organisation number 931086707. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1930. Registered share capital is NOK 100,000, divided into 665 shares. The company's stated purpose is: “Drive eiendommen Vidarsgate 13 som i det alt vesentlige tjener som bolig for selskapets aksjonærer. Tre lokaler på gateplan har næringsformål. Eiendommen og selskapets forretningskontor er i Oslo.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK −384,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK −384,000
Equity
NOK −1.3m

Financial health · 2024

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

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

Who owns AS VIDARSGATE 13?

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

Frequently asked questions about AS VIDARSGATE 13

What is the revenue of AS VIDARSGATE 13?

AS VIDARSGATE 13 had revenue of NOK 1.7m in 2024.

Where is AS VIDARSGATE 13 based?

AS VIDARSGATE 13 has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.