BIZTRAC BETA
Construction of residential and non-residential buildings

BRL AS

Org. no. 996527751 Limited company (AS) Nesodden Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 7.2m
Operating profit NOK 181,000
Equity NOK 144,000
Incorporated 2011
Employees 5
Share capital NOK 100,000

BRL AS is registered as a limited company in Nesodden, Akershus with organisation number 996527751. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2011 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Malertjenester, snekker- og andre håndverkstjenester knyttet til oppussing og rehabilitering av bygninger. Prosjektledelse og -rådgivning, fargerådgivning, stillasmontering og -utleie og andre aktiviteter tilknyttet oppussing og rehabilitering av bygninger.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.2m in revenue and NOK 181,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.2m
Operating profit
NOK 181,000
Equity
NOK 144,000
Est. value
NOK 649,000

Financial health · 2024

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

Who owns BRL AS?

JENDINE HOLDING AS
BRL AS
NOK 7.2m rev. · NOK 181,000 profit

BRL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRL AS

Who owns BRL AS?

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

What is the revenue of BRL AS?

BRL AS had revenue of NOK 7.2m in 2024.

Who is the general manager of BRL AS?

Jari Aarne Leinonen is registered as general manager of BRL AS.

Where is BRL AS based?

BRL AS has its business address in Fjellstrand.

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.