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

BRULANDSVEGEN 342 AS

Org. no. 920055249 Limited company (AS) Sunnfjord Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 265,000
Operating profit NOK 135,000
Equity NOK 550,000
Incorporated 2017
Share capital NOK 600,000

BRULANDSVEGEN 342 AS is registered as a limited company in Sunnfjord, Vestland with organisation number 920055249. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 600,000, divided into 600 shares. The company's stated purpose is: “å eie og forvalte fast eiendom, samt kjøp og salg av fast eiendom og virksomhet som står i forbindelse med dette. Herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 265,000 in revenue and NOK 135,000 in operating profit.

Key figures · 2025

Revenue
NOK 265,000
▲ +11 %
Operating profit
NOK 135,000
▼ −14 %
Equity
NOK 550,000
▼ −2 %
Est. value
NOK 480,000

Financial health · 2025

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
4.4%
Weak
Return on total assets
Solidity
18.3%
Good
Equity as a share of total capital

Who owns BRULANDSVEGEN 342 AS?

BRULANDSVEGEN 342 AS
NOK 265,000 rev. · NOK 135,000 profit

BRULANDSVEGEN 342 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRULANDSVEGEN 342 AS

Who owns BRULANDSVEGEN 342 AS?

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

What is the revenue of BRULANDSVEGEN 342 AS?

BRULANDSVEGEN 342 AS had revenue of NOK 265,000 in 2025.

Where is BRULANDSVEGEN 342 AS based?

BRULANDSVEGEN 342 AS has its business address in Førde.

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.