BIZTRAC BETA
Repair and maintenance of machinery

LINJEBORING VEST AS

Org. no. 932324911 Limited company (AS) Voss Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK −35,000
Equity NOK 178,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

LINJEBORING VEST AS is registered as a limited company in Voss, Vestland with organisation number 932324911. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Maskinering, sveising og generelle reparasjoner av stålkonstruksjoner. Salg av varer og tjenester innen mekaniske fag.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK −35,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK −35,000
Equity
NOK 178,000
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
1.12
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.6%
Good
Equity as a share of total capital

Who owns LINJEBORING VEST AS?

GODØE INVEST AS
LINJEBORING VEST AS
NOK 2.2m rev. · NOK −35,000 profit

LINJEBORING VEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LINJEBORING VEST AS

Who owns LINJEBORING VEST AS?

GODØE INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of LINJEBORING VEST AS?

LINJEBORING VEST AS had revenue of NOK 2.2m in 2025.

Who is the general manager of LINJEBORING VEST AS?

Isak Godøe is registered as general manager of LINJEBORING VEST AS.

Where is LINJEBORING VEST AS based?

LINJEBORING VEST AS has its business address in Skulestadmo.

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.