BIZTRAC BETA
General cleaning of buildings

KATZO DRIFT AS

Org. no. 997715470 Limited company (AS) Lillehammer Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 310,000
Equity NOK 1.4m
Incorporated 2011
Employees 5
Share capital NOK 100,000

KATZO DRIFT AS is registered as a limited company in Lillehammer, Innlandet with organisation number 997715470. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2011 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Tjenester innenfor rengjøring, service og vedlikeholdstjenester, konsulentvirksomhet innen fagområdet, samt deltakelse i andre selskaper og virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 310,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 310,000
Equity
NOK 1.4m
Est. value
NOK 2.1m

Financial health · 2025

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

Who owns KATZO DRIFT AS?

RUI EDGAR DO AMARAL TAVARES
KATZO DRIFT AS
NOK 2.0m rev. · NOK 310,000 profit

KATZO DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KATZO DRIFT AS

Who owns KATZO DRIFT AS?

RUI EDGAR DO AMARAL TAVARES is the largest registered owner, with 100.0%.

What is the revenue of KATZO DRIFT AS?

KATZO DRIFT AS had revenue of NOK 2.0m in 2025.

Who is the general manager of KATZO DRIFT AS?

Rui Edgar Do Amaral Tavares is registered as general manager of KATZO DRIFT AS.

Where is KATZO DRIFT AS based?

KATZO DRIFT AS has its business address in Lillehammer.

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.