BIZTRAC BETA
Rental and operating of own or leased real estate

NEDRE BARKVEDVEGEN AS

Org. no. 891472412 Limited company (AS) Strand Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 149,000
Operating profit NOK −106,000
Equity NOK 1.4m
Incorporated 2007
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−106k kr).

NEDRE BARKVEDVEGEN AS is registered as a limited company in Strand, Rogaland with organisation number 891472412. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utleie av eiendom, samt lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 149,000 in revenue and NOK −106,000 in operating profit.

Key figures · 2025

Revenue
NOK 149,000
Operating profit
NOK −106,000
Equity
NOK 1.4m
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
1.15
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
56.2%
Very good
Equity as a share of total capital

Who owns NEDRE BARKVEDVEGEN AS?

JANJA EIENDOM HOLDING AS
NEDRE BARKVEDVEGEN AS
NOK 149,000 rev. · NOK −106,000 profit

NEDRE BARKVEDVEGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NEDRE BARKVEDVEGEN AS

Who owns NEDRE BARKVEDVEGEN AS?

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

What is the revenue of NEDRE BARKVEDVEGEN AS?

NEDRE BARKVEDVEGEN AS had revenue of NOK 149,000 in 2025.

Who is the general manager of NEDRE BARKVEDVEGEN AS?

Jan Jansen is registered as general manager of NEDRE BARKVEDVEGEN AS.

Where is NEDRE BARKVEDVEGEN AS based?

NEDRE BARKVEDVEGEN AS has its business address in Jørpeland.

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.