biztrac. BETA
COMPANY REGISTER PROFILE
971281561 ORG. NO. 2018 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Activities of housing cooperatives

SAMEIET FRYDENLUNDGATEN 12

Org. no. 971281561 Condominium flat owner (ESEK) Oslo Incorporated 1988 Active
Ownership graph ↗
Revenue 2018 NOK 622,000
Operating profit NOK −47,000
Equity NOK 24,000
Incorporated 1988

Signals

2 flags
  • Driftsunderskudd 2018 Siste driftsresultat er negativt (−47k kr).
  • Nylig endring 2026-04-28 Adresseendring registrert 2026-04-28.

SAMEIET FRYDENLUNDGATEN 12 is registered as a condominium flat owner in Oslo, Oslo with organisation number 971281561. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 1988. The company's stated purpose is: “Eierseksjonssameie”. The most recent filed accounts, for the 2018 financial year, show NOK 622,000 in revenue and NOK −47,000 in operating profit.

Former names: SAMEIET FRYDENLUNDGATEN 12 V/ ADV. NILS A. ØGLAND, SAMEIET FRYDENLUNDSGATEN 12

Key figures · 2018

Revenue
NOK 622,000
▼ −23 %
Operating profit
NOK −47,000
▼ −113 %
Equity
NOK 24,000
▲ +103 %
Est. value
NOK 341,000

Financial health · 2018

Liquidity
2.06
Very good
Current assets ÷ current liabilities
Profitability
-17.8%
Not satisfactory
Return on total assets
Solidity
51.4%
Weak
Equity as a share of total capital

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

Who owns SAMEIET FRYDENLUNDGATEN 12?

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

Frequently asked questions about SAMEIET FRYDENLUNDGATEN 12

What is the revenue of SAMEIET FRYDENLUNDGATEN 12?

SAMEIET FRYDENLUNDGATEN 12 had revenue of NOK 622,000 in 2018.

Where is SAMEIET FRYDENLUNDGATEN 12 based?

SAMEIET FRYDENLUNDGATEN 12 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.