biztrac. BETA
COMPANY REGISTER PROFILE
914512921 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Landscape service activities

BUSKMENN AS

Org. no. 914512921 Limited company (AS) Bærum Incorporated 2014 Active
Revenue 2025 NOK 568,000
Operating profit NOK 85,000
Equity NOK −74,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−74k kr).

BUSKMENN AS is registered as a limited company in Bærum, Akershus with organisation number 914512921. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av anleggsgartner tjenester og produkter/tjenester som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 568,000 in revenue and NOK 85,000 in operating profit.

Key figures · 2025

Revenue
NOK 568,000
▲ +208 %
Operating profit
NOK 85,000
▲ +195 %
Equity
NOK −74,000
▲ +53 %
Est. value
NOK 554,000

Financial health · 2025

Liquidity
0.68
Weak
Current assets ÷ current liabilities
Profitability
39.7%
Very good
Return on total assets
Solidity
-25.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BUSKMENN AS?

BUSKMENN AS
NOK 568,000 rev. · NOK 85,000 profit

BUSKMENN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BUSKMENN AS

Who owns BUSKMENN AS?

Jacob Moestue is the largest registered owner, with 100.0%.

What is the revenue of BUSKMENN AS?

BUSKMENN AS had revenue of NOK 568,000 in 2025.

Who is the general manager of BUSKMENN AS?

Jacob Moestue is registered as general manager of BUSKMENN AS.

Where is BUSKMENN AS based?

BUSKMENN AS has its business address in Jar.

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.