BIZTRAC BETA
Interior design activities

ZEBRA BYGGPARTNER AS

Org. no. 913756959 Limited company (AS) Bamble Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 24,000
Equity NOK 457,000
Incorporated 2014
Share capital NOK 30,000

ZEBRA BYGGPARTNER AS is registered as a limited company in Bamble, Telemark with organisation number 913756959. The business is classified under interior design activities (NACE 74.130). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investere i andre selskaper, drive med kjøp og salg av fast eiendom samt yte konsulenttjenester innen entreprenørbransjen. Selskapets formål er også å kunne bidra med midler til kristne foreninger, menigheter og stiftelser.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 24,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 24,000
Equity
NOK 457,000
Est. value
NOK 299,000

Financial health · 2025

Liquidity
1.58
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.1%
Good
Equity as a share of total capital

Who owns ZEBRA BYGGPARTNER AS?

REALF KNUTSEN
ZEBRA BYGGPARTNER AS
NOK 2.6m rev. · NOK 24,000 profit

ZEBRA BYGGPARTNER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ZEBRA BYGGPARTNER AS

Who owns ZEBRA BYGGPARTNER AS?

REALF KNUTSEN is the largest registered owner, with 100.0%.

What is the revenue of ZEBRA BYGGPARTNER AS?

ZEBRA BYGGPARTNER AS had revenue of NOK 2.6m in 2025.

Who is the general manager of ZEBRA BYGGPARTNER AS?

Realf Knutsen is registered as general manager of ZEBRA BYGGPARTNER AS.

Where is ZEBRA BYGGPARTNER AS based?

ZEBRA BYGGPARTNER AS has its business address in Stathelle.

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.