BIZTRAC BETA
Rental and operating of own or leased real estate

BREIDABLIKKTUN EIENDOM AS

Org. no. 984607954 Limited company (AS) Haugesund Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 634,000
Operating profit NOK 359,000
Equity NOK 2.0m
Incorporated 2002
Share capital NOK 1.0m

BREIDABLIKKTUN EIENDOM AS is registered as a limited company in Haugesund, Rogaland with organisation number 984607954. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 1.0m, divided into 10000 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 634,000 in revenue and NOK 359,000 in operating profit.

Key figures · 2024

Revenue
NOK 634,000
Operating profit
NOK 359,000
Equity
NOK 2.0m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns BREIDABLIKKTUN EIENDOM AS?

EASYPEASY AS
BREIDABLIKKTUN EIENDOM AS
NOK 634,000 rev. · NOK 359,000 profit

BREIDABLIKKTUN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BREIDABLIKKTUN EIENDOM AS

Who owns BREIDABLIKKTUN EIENDOM AS?

EASYPEASY AS is the largest registered owner, with 100.0%.

What is the revenue of BREIDABLIKKTUN EIENDOM AS?

BREIDABLIKKTUN EIENDOM AS had revenue of NOK 634,000 in 2024.

Who is the general manager of BREIDABLIKKTUN EIENDOM AS?

Gustav Lie Rugtveit is registered as general manager of BREIDABLIKKTUN EIENDOM AS.

Where is BREIDABLIKKTUN EIENDOM AS based?

BREIDABLIKKTUN EIENDOM AS has its business address in Haugesund.

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.