BIZTRAC BETA
Development of building projects

BE RØRA AS

Org. no. 930490814 Limited company (AS) Levanger Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 818,000
Operating profit NOK 613,000
Equity NOK 53.4m
Incorporated 2022
Share capital NOK 1.0m

Signals

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

BE RØRA AS is registered as a limited company in Levanger, Trøndelag with organisation number 930490814. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2022. Registered share capital is NOK 1.0m, divided into 30000 shares. The company's stated purpose is: “Bygge-, eiendoms- og handelsvirksomhet og hva dermed står i forbindelse, herunder ved aksjeinnskudd eller annen måte delta i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 818,000 in revenue and NOK 613,000 in operating profit.

Key figures · 2025

Revenue
NOK 818,000
Operating profit
NOK 613,000
Equity
NOK 53.4m
Est. value
NOK 37.8m

Financial health · 2025

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.1%
Good
Equity as a share of total capital

Who owns BE RØRA AS?

BERG EIENDOM LEVANGER AS
BE RØRA AS
NOK 818,000 rev. · NOK 613,000 profit

BE RØRA AS has 11 registered shareholders:

All shareholders and roles →

Frequently asked questions about BE RØRA AS

Who owns BE RØRA AS?

BERG EIENDOM LEVANGER AS is the largest registered owner, with 66.0%.

What is the revenue of BE RØRA AS?

BE RØRA AS had revenue of NOK 818,000 in 2025.

Who is the general manager of BE RØRA AS?

Odd Einar Aarmo is registered as general manager of BE RØRA AS.

Where is BE RØRA AS based?

BE RØRA AS has its business address in Levanger.

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.