BIZTRAC BETA
Rental and operating of own or leased real estate

BEDRIFTSVEGEN 11 AS

Org. no. 927990342 Limited company (AS) Skien Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 709,000
Operating profit NOK 340,000
Equity NOK 466,000
Incorporated 2021
Share capital NOK 30,000

BEDRIFTSVEGEN 11 AS is registered as a limited company in Skien, Telemark with organisation number 927990342. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Handel, utvikling, kjøp, salg og utleie av fast eiendom og annen virksomhet som naturlig faller inn under dette, ved aksjekjøp eller på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 709,000 in revenue and NOK 340,000 in operating profit.

Key figures · 2024

Revenue
NOK 709,000
Operating profit
NOK 340,000
Equity
NOK 466,000
Est. value
NOK 979,000

Financial health · 2024

Liquidity
5.44
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
23.5%
Good
Equity as a share of total capital

Who owns BEDRIFTSVEGEN 11 AS?

TRIANGELEN EIENDOMSSELSKAP AS
BEDRIFTSVEGEN 11 AS
NOK 709,000 rev. · NOK 340,000 profit

BEDRIFTSVEGEN 11 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BEDRIFTSVEGEN 11 AS

Who owns BEDRIFTSVEGEN 11 AS?

TRIANGELEN EIENDOMSSELSKAP AS is the largest registered owner, with 100.0%.

What is the revenue of BEDRIFTSVEGEN 11 AS?

BEDRIFTSVEGEN 11 AS had revenue of NOK 709,000 in 2024.

Who is the general manager of BEDRIFTSVEGEN 11 AS?

Guro Ingeborg Erikstein is registered as general manager of BEDRIFTSVEGEN 11 AS.

Where is BEDRIFTSVEGEN 11 AS based?

BEDRIFTSVEGEN 11 AS has its business address in Skien.

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.