BIZTRAC BETA
COMPANY REGISTER PROFILE
823198132 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Civil engineering activities

LINJALEN AS

Org. no. 823198132 Limited company (AS) Marker Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −81,000
Equity NOK 146,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

LINJALEN AS is registered as a limited company in Marker, Østfold with organisation number 823198132. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Rådgivning innen byggeprosesser.”.

Key figures · 2025

Operating profit
NOK −81,000
Equity
NOK 146,000
Est. value
NOK 237,000

Financial health · 2025

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

Who owns LINJALEN AS?

LINJALEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LINJALEN AS

Who owns LINJALEN AS?

ODD IVAR HALVORSRUD is the largest registered owner, with 90.0%.

Who is the general manager of LINJALEN AS?

Kristin Brath is registered as general manager of LINJALEN AS.

Where is LINJALEN AS based?

LINJALEN AS has its business address in Ørje.

Property

Business address Lyngveien 5, 1870 Ørje
Cadastral unit 3122-90/230/0/0
Building Enebolig · 1 unit

4 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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