BIZTRAC BETA
Site preparation

ODDBJØRN STRAND MASKIN AS

Org. no. 913625803 Limited company (AS) Nordre Land Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 58,000
Operating profit NOK −138,000
Equity NOK 122,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

ODDBJØRN STRAND MASKIN AS is registered as a limited company in Nordre Land, Innlandet with organisation number 913625803. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Transport på veg, utleie av traktor og krokhenger. Drift av jordbruk og hva herved står i forbindelse. Selskapet kan til like investere i selskap og annen forretningsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 58,000 in revenue and NOK −138,000 in operating profit.

Key figures · 2024

Revenue
NOK 58,000
Operating profit
NOK −138,000
Equity
NOK 122,000
Est. value
NOK 125,000

Financial health · 2024

Liquidity
-4.16
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
53.4%
Very good
Equity as a share of total capital

Who owns ODDBJØRN STRAND MASKIN AS?

ODDBJØRN STRAND
ODDBJØRN STRAND MASKIN AS
NOK 58,000 rev. · NOK −138,000 profit

ODDBJØRN STRAND MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ODDBJØRN STRAND MASKIN AS

Who owns ODDBJØRN STRAND MASKIN AS?

ODDBJØRN STRAND is the largest registered owner, with 100.0%.

What is the revenue of ODDBJØRN STRAND MASKIN AS?

ODDBJØRN STRAND MASKIN AS had revenue of NOK 58,000 in 2024.

Where is ODDBJØRN STRAND MASKIN AS based?

ODDBJØRN STRAND MASKIN AS has its business address in Aust-Torpa.

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.