BIZTRAC BETA
Rental and operating of own or leased real estate

KRIVI AS

Org. no. 916363842 Limited company (AS) Ålesund Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 734,000
Operating profit NOK 383,000
Equity NOK 990,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KRIVI AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 916363842. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Erverv, utvikling, forvaltning, omsetning og utleie av fast eiendom, samt utleie og drift av maskiner og utstyr til bygge og anleggsnæringen.”. The most recent filed accounts, for the 2025 financial year, show NOK 734,000 in revenue and NOK 383,000 in operating profit.

Key figures · 2025

Revenue
NOK 734,000
Operating profit
NOK 383,000
Equity
NOK 990,000
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
8.65
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.6%
Satisfactory
Equity as a share of total capital

Who owns KRIVI AS?

E A SKAR INVEST AS
KRIVI AS
NOK 734,000 rev. · NOK 383,000 profit

KRIVI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KRIVI AS

Who owns KRIVI AS?

E A SKAR INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of KRIVI AS?

KRIVI AS had revenue of NOK 734,000 in 2025.

Who is the general manager of KRIVI AS?

Eldar Arne Skar is registered as general manager of KRIVI AS.

Where is KRIVI AS based?

KRIVI AS has its business address in Ålesund.

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.