BIZTRAC BETA
Rental and operating of own or leased real estate

KRABY EIENDOM AS

Org. no. 921824319 Limited company (AS) Østre Toten Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 569,000
Operating profit NOK 339,000
Equity NOK 4.2m
Incorporated 2018
Share capital NOK 101,000

Signals

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

KRABY EIENDOM AS is registered as a limited company in Østre Toten, Innlandet with organisation number 921824319. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 101,000, divided into 1013 shares. The company's stated purpose is: “Erverv og drift av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 569,000 in revenue and NOK 339,000 in operating profit.

Key figures · 2024

Revenue
NOK 569,000
Operating profit
NOK 339,000
Equity
NOK 4.2m
Est. value
NOK 3.8m

Financial health · 2024

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

Who owns KRABY EIENDOM AS?

BRØDRENE GUDBRANDSEN AS
KRABY EIENDOM AS
NOK 569,000 rev. · NOK 339,000 profit

KRABY EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KRABY EIENDOM AS

Who owns KRABY EIENDOM AS?

BRØDRENE GUDBRANDSEN AS is the largest registered owner, with 100.0%.

What is the revenue of KRABY EIENDOM AS?

KRABY EIENDOM AS had revenue of NOK 569,000 in 2024.

Who is the general manager of KRABY EIENDOM AS?

Nils Olav Gudbrandsen is registered as general manager of KRABY EIENDOM AS.

Where is KRABY EIENDOM AS based?

KRABY EIENDOM AS has its business address in Lena.

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.