I'd say "just call your route" but it seems that your design actually hasn't any routes...but I come to that later.
So for now you've got to
- Call the script again, checking if the method by which the site was called is POST and then call your Controller method
- Create a second script, maybe called
registreer.php which is called when submitting the form, where you call the Controller method
The above example will not work, because you're basically calling your method Controller::registreer() and inserting the returned results from it (if it has any, in this case it hasn't) into the action attribute from your <form> tag.
If you want to actually have the file registreer.php to be called on form submission just write it into the action attribute.
Anyway, that's not a quite good design - due to the fact that your going to have some kind of Controller in your code it would be the best practice to actually create Routes which are calling methods you define.
Have a look at this tutorial to get a clue about what MVC actually is.
After that I recommend you to use one of the many many many MVC frameworks available out there.
Two of my favorites are
- Silex, a micro framework, mainly giving you the change to create fast and easily routes for your application
- Slim, yet another micro framework
- Laravel, nice to use framework
If you think you've got the idea and want to get deeper, have a look at the "bigger" frameworks, like
- Symfony2, not just a MVC framework, comes with a bunch of additional components (called bundles)
- Zend Framework, another one
Those are just five examples of many frameworks out there. Go and grab one.