biztrac. BETA
COMPANY REGISTER PROFILE
911620928 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

BEDRIFTSVEIEN 20 AS

Org. no. 911620928 Limited company (AS) Sandnes Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 3.7m
Operating profit NOK 1.9m
Equity NOK 6.0m
Incorporated 2013
Share capital NOK 5.1m

BEDRIFTSVEIEN 20 AS is registered as a limited company in Sandnes, Rogaland with organisation number 911620928. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 5.1m, divided into 100 shares. The company's stated purpose is: “Eiendoms- og finansielle investeringer, utleie næringseiendom, samt eventuell deltakelse i tilsvarende virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.7m in revenue and NOK 1.9m in operating profit.

Key figures · 2025

Revenue
NOK 3.7m
▲ +2 %
Operating profit
NOK 1.9m
▲ +27 %
Equity
NOK 6.0m
▼ −3 %
Est. value
NOK 6.3m

Financial health · 2025

Liquidity
0.55
Weak
Current assets ÷ current liabilities
Profitability
6.6%
Satisfactory
Return on total assets
Solidity
21.1%
Good
Equity as a share of total capital

Who owns BEDRIFTSVEIEN 20 AS?

BEDRIFTSVEIEN 20 AS
NOK 3.7m rev. · NOK 1.9m profit

BEDRIFTSVEIEN 20 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BEDRIFTSVEIEN 20 AS

Who owns BEDRIFTSVEIEN 20 AS?

VIBEMYR EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of BEDRIFTSVEIEN 20 AS?

BEDRIFTSVEIEN 20 AS had revenue of NOK 3.7m in 2025.

Who is the general manager of BEDRIFTSVEIEN 20 AS?

Sondre Falch is registered as general manager of BEDRIFTSVEIEN 20 AS.

Where is BEDRIFTSVEIEN 20 AS based?

BEDRIFTSVEIEN 20 AS has its business address in Sandnes.

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

Report a problem

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