BIZTRAC BETA
Buying and selling of own real estate

MONEYMAKER AS

Org. no. 980368300 Limited company (AS) Lier Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 3.1m
Operating profit NOK 369,000
Equity NOK 123.7m
Incorporated 1998
Share capital NOK 100,000

MONEYMAKER AS is registered as a limited company in Lier, Buskerud with organisation number 980368300. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 1998. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom. Eie aksjer, andeler og andre finansielle aktiva. Utleie av maskiner og utstyr samt entreprenørvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.1m in revenue and NOK 369,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.1m
Operating profit
NOK 369,000
Equity
NOK 123.7m
Est. value
NOK 87.0m

Financial health · 2024

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

Who owns MONEYMAKER AS?

THOMAS SAKARI PETTERSEN
MONEYMAKER AS
NOK 3.1m rev. · NOK 369,000 profit

MONEYMAKER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MONEYMAKER AS own?

MONEYMAKER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MONEYMAKER AS

Who owns MONEYMAKER AS?

THOMAS SAKARI PETTERSEN is the largest registered owner, with 100.0%.

What is the revenue of MONEYMAKER AS?

MONEYMAKER AS had revenue of NOK 3.1m in 2024.

Who is the general manager of MONEYMAKER AS?

Thomas Sakari Pettersen is registered as general manager of MONEYMAKER AS.

Where is MONEYMAKER AS based?

MONEYMAKER AS has its business address in Sylling.

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.