BIZTRAC BETA
COMPANY REGISTER PROFILE
814306232 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Plumbing installation

BÅ EIENDOM AS

Org. no. 814306232 Limited company (AS) Flekkefjord Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 1.1m
Equity NOK 366,000
Incorporated 2014
Share capital NOK 100,000

Signals

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

BÅ EIENDOM AS is registered as a limited company in Flekkefjord, Agder with organisation number 814306232. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Utleie og drift av fast eiendom samt hva som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
▲ +9 %
Operating profit
NOK 1.1m
▲ +35 %
Equity
NOK 366,000
▼ −65 %
Est. value
NOK 1.9m

Financial health · 2025

Liquidity
0.91
Weak
Current assets ÷ current liabilities
Profitability
9.4%
Satisfactory
Return on total assets
Solidity
3.3%
Weak
Equity as a share of total capital

Who owns BÅ EIENDOM AS?

BÅ EIENDOM AS
NOK 1.9m rev. · NOK 1.1m profit

BÅ EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BÅ EIENDOM AS

Who owns BÅ EIENDOM AS?

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

What is the revenue of BÅ EIENDOM AS?

BÅ EIENDOM AS had revenue of NOK 1.9m in 2025.

Who is the general manager of BÅ EIENDOM AS?

Jan Rune Åsly is registered as general manager of BÅ EIENDOM AS.

Where is BÅ EIENDOM AS based?

BÅ EIENDOM AS has its business address in Flekkefjord.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.