biztrac. BETA
COMPANY REGISTER PROFILE
914778050 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Sawmilling and planing of wood

IMO BRUK AS

Org. no. 914778050 Limited company (AS) Sandefjord Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK −106,000
Equity NOK 356,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

IMO BRUK AS is registered as a limited company in Sandefjord, Vestfold with organisation number 914778050. The business is classified under sawmilling and planing of wood (NACE 16.110). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Sagbruksvirksomhet med tilhørende videreforedling av trelast til produkter som blant annet paller og lemmer.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK −106,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
▲ +66 %
Operating profit
NOK −106,000
▲ +40 %
Equity
NOK 356,000
▼ −24 %
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
1.51
Good
Current assets ÷ current liabilities
Profitability
-15.8%
Not satisfactory
Return on total assets
Solidity
72.7%
Very good
Equity as a share of total capital

Who owns IMO BRUK AS?

IMO BRUK AS
NOK 2.8m rev. · NOK −106,000 profit

IMO BRUK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about IMO BRUK AS

Who owns IMO BRUK AS?

Johan Martin Osmundsen is the largest registered owner, with 100.0%.

What is the revenue of IMO BRUK AS?

IMO BRUK AS had revenue of NOK 2.8m in 2025.

Who is the general manager of IMO BRUK AS?

Johan Martin Osmundsen is registered as general manager of IMO BRUK AS.

Where is IMO BRUK AS based?

IMO BRUK AS has its business address in Kodal.

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.