BIZTRAC BETA
Rental and operating of own or leased real estate

BREISETHVEGEN 3 AS

Org. no. 830869832 Limited company (AS) Lillehammer Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 767,000
Operating profit NOK 332,000
Equity NOK 24,000
Incorporated 2023
Share capital NOK 30,000

BREISETHVEGEN 3 AS is registered as a limited company in Lillehammer, Innlandet with organisation number 830869832. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøpe, selge, eie, leie ut, utvikle og drifte fast eiendom, samt eie aksjer og andeler i andre selskap og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 767,000 in revenue and NOK 332,000 in operating profit.

Key figures · 2024

Revenue
NOK 767,000
Operating profit
NOK 332,000
Equity
NOK 24,000
Est. value
NOK 291,000

Financial health · 2025

Liquidity
3.74
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BREISETHVEGEN 3 AS?

PER LØBERG ERIKSEN
BREISETHVEGEN 3 AS
NOK 767,000 rev. · NOK 332,000 profit

BREISETHVEGEN 3 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BREISETHVEGEN 3 AS er morselskap for 1 datterselskap:

Frequently asked questions about BREISETHVEGEN 3 AS

Who owns BREISETHVEGEN 3 AS?

PER LØBERG ERIKSEN is the largest registered owner, with 100.0%.

What is the revenue of BREISETHVEGEN 3 AS?

BREISETHVEGEN 3 AS had revenue of NOK 767,000 in 2024.

Where is BREISETHVEGEN 3 AS based?

BREISETHVEGEN 3 AS has its business address in Lillehammer.

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.