biztrac. BETA
COMPANY REGISTER PROFILE
935740797 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

KRI18 AS

Org. no. 935740797 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −1.5m
Equity NOK 5.5m
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,5 mill kr).

KRI18 AS is registered as a limited company in Oslo, Oslo with organisation number 935740797. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, utvikling og salg av fast eiendom, investering i verdipapirer og andre formuesobjekter, herunder deltakelse i andre selskaper med lignende virksomhet. Samt virksomhet som relateres til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −1.5m in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −1.5m
Equity
NOK 5.5m
Est. value
NOK 24.3m

Financial health · 2025

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

Who owns KRI18 AS?

KRI18 AS
NOK 0 rev. · NOK −1.5m profit

KRI18 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KRI18 AS

Who owns KRI18 AS?

RØSBERG AMUNDSEN EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of KRI18 AS?

KRI18 AS had revenue of NOK 0 in 2025.

Who is the general manager of KRI18 AS?

Nicholai Pihl is registered as general manager of KRI18 AS.

Where is KRI18 AS based?

KRI18 AS 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.