BIZTRAC BETA
Rental and operating of own or leased real estate

NIKOLAIKIRKEALMENNING 2 AS

Org. no. 968248162 Limited company (AS) Bergen Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 245,000
Operating profit NOK 124,000
Equity NOK −500,000
Incorporated 1993
Share capital NOK 450,000

Signals

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

NIKOLAIKIRKEALMENNING 2 AS is registered as a limited company in Bergen, Vestland with organisation number 968248162. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1993. Registered share capital is NOK 450,000. The company's stated purpose is: “Kjøpe og drive utleie av den faste eiendommen Nikolaikirkealmenning 2.”. The most recent filed accounts, for the 2024 financial year, show NOK 245,000 in revenue and NOK 124,000 in operating profit.

Key figures · 2024

Revenue
NOK 245,000
Operating profit
NOK 124,000
Equity
NOK −500,000
Est. value
NOK 534,000

Financial health · 2024

Liquidity
0.33
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-36.9%
Weak
Equity as a share of total capital

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

Who owns NIKOLAIKIRKEALMENNING 2 AS?

CHRISTIAN RYGG
NIKOLAIKIRKEALMENNING 2 AS
NOK 245,000 rev. · NOK 124,000 profit

NIKOLAIKIRKEALMENNING 2 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NIKOLAIKIRKEALMENNING 2 AS

Who owns NIKOLAIKIRKEALMENNING 2 AS?

CHRISTIAN RYGG is the largest registered owner, with 51.1%.

What is the revenue of NIKOLAIKIRKEALMENNING 2 AS?

NIKOLAIKIRKEALMENNING 2 AS had revenue of NOK 245,000 in 2024.

Where is NIKOLAIKIRKEALMENNING 2 AS based?

NIKOLAIKIRKEALMENNING 2 AS has its business address in Bergen.

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.