BIZTRAC BETA
Rental and operating of own or leased real estate

BAKKELY AS

Org. no. 918392203 Limited company (AS) Ullensvang Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 336,000
Operating profit NOK 242,000
Equity NOK 1.6m
Incorporated 2017
Share capital NOK 1.5m

Signals

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

BAKKELY AS is registered as a limited company in Ullensvang, Vestland with organisation number 918392203. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 1.5m, divided into 1475 shares. The company's stated purpose is: “Eie og drifte fast eiendom og det som naturlig står i forbindelse med dette, samt å investere og delta i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 336,000 in revenue and NOK 242,000 in operating profit.

Key figures · 2025

Revenue
NOK 336,000
Operating profit
NOK 242,000
Equity
NOK 1.6m
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns BAKKELY AS?

HORDATUN DRIFT AS
BAKKELY AS
NOK 336,000 rev. · NOK 242,000 profit

BAKKELY AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BAKKELY AS

Who owns BAKKELY AS?

HORDATUN DRIFT AS is the largest registered owner, with 67.8%.

What is the revenue of BAKKELY AS?

BAKKELY AS had revenue of NOK 336,000 in 2025.

Who is the general manager of BAKKELY AS?

Randi Tokheim Legård is registered as general manager of BAKKELY AS.

Where is BAKKELY AS based?

BAKKELY AS has its business address in Røldal.

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.