BIZTRAC BETA
Other technical consultancy

BAUTZ INVEST AS

Org. no. 991956964 Limited company (AS) Lier Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 211,000
Operating profit NOK 18,000
Equity NOK 27.4m
Incorporated 2007
Share capital NOK 100,000

BAUTZ INVEST AS is registered as a limited company in Lier, Buskerud with organisation number 991956964. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investeringer, eiendomsutvikling og salg, og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 211,000 in revenue and NOK 18,000 in operating profit.

Key figures · 2024

Revenue
NOK 211,000
Operating profit
NOK 18,000
Equity
NOK 27.4m
Est. value
NOK 13.5m

Financial health · 2024

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

Who owns BAUTZ INVEST AS?

ANDRE MELBØE BAUTZ
BAUTZ INVEST AS
NOK 211,000 rev. · NOK 18,000 profit

BAUTZ INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BAUTZ INVEST AS

Who owns BAUTZ INVEST AS?

ANDRE MELBØE BAUTZ is the largest registered owner, with 100.0%.

What is the revenue of BAUTZ INVEST AS?

BAUTZ INVEST AS had revenue of NOK 211,000 in 2024.

Who is the general manager of BAUTZ INVEST AS?

Andre Melbøe Bautz is registered as general manager of BAUTZ INVEST AS.

Where is BAUTZ INVEST AS based?

BAUTZ INVEST 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.