BIZTRAC BETA
Wholesale of agricultural machinery, equipment and supplies

LANGERØD AS

Org. no. 988964468 Limited company (AS) Tønsberg Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK −595,000
Equity NOK 11.6m
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−595k kr).

LANGERØD AS is registered as a limited company in Tønsberg, Vestfold with organisation number 988964468. The business is classified under wholesale of agricultural machinery, equipment and supplies (NACE 46.610). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investere i fast eiendom, aksjer og andre verdipapirer, valuta, annen virksomhet samt øvrige investeringer av enhver art, og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK −595,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK −595,000
Equity
NOK 11.6m
Est. value
NOK 61.4m

Financial health · 2024

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

Who owns LANGERØD AS?

MORTEN FREBERG
LANGERØD AS
NOK 1.7m rev. · NOK −595,000 profit

LANGERØD AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LANGERØD AS own?

LANGERØD AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LANGERØD AS

Who owns LANGERØD AS?

MORTEN FREBERG is the largest registered owner, with 51.0%.

What is the revenue of LANGERØD AS?

LANGERØD AS had revenue of NOK 1.7m in 2024.

Where is LANGERØD AS based?

LANGERØD AS has its business address in Barkåker.

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.