BIZTRAC BETA
Rental and operating of own or leased real estate

BIRKELANDSVEGEN 84 AS

Org. no. 923171630 Limited company (AS) Sauda Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 321,000
Operating profit NOK 367,000
Equity NOK 163,000
Incorporated 2019
Share capital NOK 30,000

BIRKELANDSVEGEN 84 AS is registered as a limited company in Sauda, Rogaland with organisation number 923171630. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utvikling, drift og forvalting, herunder kjøp og salg av fast eiendom og samt hva her står i forbindelse, herunder å delta i andre foretakender.”. The most recent filed accounts, for the 2025 financial year, show NOK 321,000 in revenue and NOK 367,000 in operating profit.

Key figures · 2025

Revenue
NOK 321,000
Operating profit
NOK 367,000
Equity
NOK 163,000
Est. value
NOK 753,000

Financial health · 2025

Liquidity
0.90
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.2%
Weak
Equity as a share of total capital

Who owns BIRKELANDSVEGEN 84 AS?

ATEME HOLDING AS
BIRKELANDSVEGEN 84 AS
NOK 321,000 rev. · NOK 367,000 profit

BIRKELANDSVEGEN 84 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BIRKELANDSVEGEN 84 AS

Who owns BIRKELANDSVEGEN 84 AS?

ATEME HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BIRKELANDSVEGEN 84 AS?

BIRKELANDSVEGEN 84 AS had revenue of NOK 321,000 in 2025.

Who is the general manager of BIRKELANDSVEGEN 84 AS?

Asle Rafdal is registered as general manager of BIRKELANDSVEGEN 84 AS.

Where is BIRKELANDSVEGEN 84 AS based?

BIRKELANDSVEGEN 84 AS has its business address in Sauda.

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.