biztrac. BETA
COMPANY REGISTER PROFILE
931119680 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

KRØGLI EIENDOM AS

Org. no. 931119680 Limited company (AS) Færder Incorporated 2023 Active
Revenue 2025 NOK 2.7m
Operating profit NOK −184,000
Equity NOK −150,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

KRØGLI EIENDOM AS is registered as a limited company in Færder, Vestfold with organisation number 931119680. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg utleie service tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK −184,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
▲ +187 %
Operating profit
NOK −184,000
▼ −442 %
Equity
NOK −150,000
▼ −392 %

Financial health · 2025

Liquidity
0.77
Weak
Current assets ÷ current liabilities
Profitability
-99.3%
Not satisfactory
Return on total assets
Solidity
-65.2%
Weak
Equity as a share of total capital

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

Who owns KRØGLI EIENDOM AS?

KRØGLI EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about KRØGLI EIENDOM AS

Who owns KRØGLI EIENDOM AS?

Jan Krøgli is the largest registered owner, with 30.0%.

What is the revenue of KRØGLI EIENDOM AS?

KRØGLI EIENDOM AS had revenue of NOK 2.7m in 2025.

Who is the general manager of KRØGLI EIENDOM AS?

Jan Krøgli is registered as general manager of KRØGLI EIENDOM AS.

Where is KRØGLI EIENDOM AS based?

KRØGLI EIENDOM AS has its business address in Torød.

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.