BIZTRAC BETA
COMPANY REGISTER PROFILE
932076861 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

AS OLE MOSS BRUK

Org. no. 932076861 Limited company (AS) Sør-Odal Incorporated 1926 Active
Ownership graph ↗
Revenue 2025 NOK 206,000
Operating profit NOK 90,000
Equity NOK 998,000
Incorporated 1926
Share capital NOK 115,000

AS OLE MOSS BRUK is registered as a limited company in Sør-Odal, Innlandet with organisation number 932076861. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1926. Registered share capital is NOK 115,000, divided into 192 shares. The company's stated purpose is: “Kjøpe, eie og drive eiendommer, samt annen forretningsmessig virksomhet som naturlig hører inn under dette, herunder deltakelse i andre selskaper av enhver art.”. The most recent filed accounts, for the 2025 financial year, show NOK 206,000 in revenue and NOK 90,000 in operating profit.

Key figures · 2025

Revenue
NOK 206,000
▲ +7 %
Operating profit
NOK 90,000
▼ −1 %
Equity
NOK 998,000
▲ +11 %
Est. value
NOK 989,000

Financial health · 2025

Liquidity
23.94
Very good
Current assets ÷ current liabilities
Profitability
11.9%
Good
Return on total assets
Solidity
97.6%
Very good
Equity as a share of total capital

Who owns AS OLE MOSS BRUK?

AS OLE MOSS BRUK has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about AS OLE MOSS BRUK

Who owns AS OLE MOSS BRUK?

MARI PRAN is the largest registered owner, with 20.8%.

What is the revenue of AS OLE MOSS BRUK?

AS OLE MOSS BRUK had revenue of NOK 206,000 in 2025.

Who is the general manager of AS OLE MOSS BRUK?

Hans Marcus Moss is registered as general manager of AS OLE MOSS BRUK.

Where is AS OLE MOSS BRUK based?

AS OLE MOSS BRUK has its business address in Disenå.

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.