BIZTRAC BETA
Rental and operating of own or leased real estate

LANGEBRU EIENDOM AS

Org. no. 929649273 Limited company (AS) Drammen Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 908,000
Operating profit NOK 675,000
Equity NOK 1.7m
Incorporated 2022
Share capital NOK 30,000

Signals

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

LANGEBRU EIENDOM AS is registered as a limited company in Drammen, Buskerud with organisation number 929649273. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 50 shares. The company's stated purpose is: “Å eie og forvalte fast eiendom og virksomhet som står i forbindelse med dette, herunder å eie andeler og aksjer i andre selskaper med likeartet formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 908,000 in revenue and NOK 675,000 in operating profit.

Key figures · 2025

Revenue
NOK 908,000
Operating profit
NOK 675,000
Equity
NOK 1.7m
Est. value
NOK 2.6m

Financial health · 2024

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

Who owns LANGEBRU EIENDOM AS?

RFP AS
LANGEBRU EIENDOM AS
NOK 908,000 rev. · NOK 675,000 profit

LANGEBRU EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LANGEBRU EIENDOM AS

Who owns LANGEBRU EIENDOM AS?

RFP AS is the largest registered owner, with 100.0%.

What is the revenue of LANGEBRU EIENDOM AS?

LANGEBRU EIENDOM AS had revenue of NOK 908,000 in 2025.

Where is LANGEBRU EIENDOM AS based?

LANGEBRU EIENDOM AS has its business address in Drammen.

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.