BIZTRAC BETA
COMPANY REGISTER PROFILE
934145291 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Activities of housing cooperatives

LINDERUDLØKKA FELT C BRL

Org. no. 934145291 Housing cooperative (BRL) Oslo Incorporated 2024 Active
Ownership graph ↗
Equity NOK 10,000
Incorporated 2024

LINDERUDLØKKA FELT C BRL is registered as a housing cooperative in Oslo, Oslo with organisation number 934145291. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2024. The company's stated purpose is: “Borettslag”.

Key figures · 2025

Equity
NOK 10,000
Est. value
NOK 5,000

Financial health · 2025

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

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

Who owns LINDERUDLØKKA FELT C BRL?

No shareholders are registered for LINDERUDLØKKA FELT C BRL in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about LINDERUDLØKKA FELT C BRL

Who is the general manager of LINDERUDLØKKA FELT C BRL?

Richard Stanislav Thomasson Zagar is registered as general manager of LINDERUDLØKKA FELT C BRL.

Where is LINDERUDLØKKA FELT C BRL based?

LINDERUDLØKKA FELT C BRL has its business address in Oslo.

Property

Business address c/o Stor-Oslo Eiendom AS Dronning Eufemias gate 16, 0191 Oslo
Cadastral unit 301-234/83/0/0
Building Kontor- og administrasjonsbygning, rådhus · 3 units

891 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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